Now I'm also on #Usenet via Eternal September. To my surprise, #Emacs #Gnus was easier to set up than its documentation initially promised...

Having followed a tutorial, I could make #WireGuard wg-quick work on my #OpenBSD, but not without DNS query leaks, so I learned I must figure out #unbound - however, a noob like me can only seem to manage to fix configuration errors while unbound itself apparently won't start because of this (which I found out after learning there's more than one way to debug unbound - not elegant, imho):

[1781449588] unbound[95585:0] error: bind: address already in use
[1781449588] unbound[95585:0] fatal error: could not open ports

I figured I should add my VPN interfaces to unbound.conf, but other than that I'm still clueless what else do I need to add or delete.

Thanks for your patience.

Has anyone here switched from Let's Encrypt to Actalis?

Thought-provoking words on #NetBSD posted by someone from Reddit who seems to know their stuff (https://old.reddit.com/r/openbsd/comments/1tki5xp/how_long_have_you_all_been_using_openbsd/oo2fa39/):

"NetBSD is a fine project. It just isn't on-par with OpenBSD's support for things it claims to support. Linux's kernel+GNU userspace would still work fine for many systems that NetBSD/OpenBSD supports if they wouldn't have started going all-in on adopting things like Rust."

"...while [NetBSD] claims to support a lot of old hardware and it does to some extent they are not doing as much testing as the OpenBSD project does. I can always be sure if OpenBSD claims to support a piece of hardware that it'll at least boot on it. This isn't true of NetBSD. There are a lot of older architectures NetBSD claims to support but if you attempt to install NetBSD on them you'll quickly run into various types of errors (if it boots at all). They just don't seem to have enough man power to keep support going for a lot of things they used to support or they aren't testing current versions of their OS on them. Most likely, whomever initially ported NetBSD over years ago just hasn't checked in awhile. But the release notes and man pages rarely seem to get updated.

This isn't 100% their fault. It's hard to keep a lot of things building on older architectures and machines now. Since a lot of projects have left everything but x86 and ARM behind and don't care if they break support for things outside of those two architectures. Hell even within x86 and ARM they don't care if they break 32-bit support and now expect you to run 64-bit."