It’s kinda hard not getting jaded when entitled people (or companies) expect commercial grade support for something you work on your free time for pennies or for free, and to top that usually are pretty abusive from the get go.

Sweeney has had a chip on his shoulder with Linux for at least 15 years. It’s honestly a bit weird since if you look at stuff before around 2005, he had quite a different tone.

Video demonstration

Bird species, most of the time. I look for a bird that seems to have some connection with the intended purpose of the box, then use that. e.g. my work computer’s hostname is cormorant.

I guess it would’ve been a bulletting board system that people used a 14k modem to connect to, one at a time, and it would completely block the phone line.

My parents weren’t thrilled, but hey, we had a message board and LORD running there.

I am placing careful (nevermind that, this seems very nice) interest in this.

Few questions (since I’m on mobile, and it’ll take me a while to get back to my computer to find out for myself):

• How does managing sieve work with this?
• Does it play along with rspamd?
• Is it tested on x64_64 only?
• Does it support PGP, can email be encrypted-at-rest using this?
• Is there a way to run this behind a reverse proxy that handles the certificates? I’m not too keen on dealing with two separate sets of those in separate places.
• Does this require LDAP?

If missing, are those on roadmap?

Vaultwarden and git are in daily use. Everything else comes far behind.

I’d recommend going with the vanilla Raspberry Pi OS then. Sure, it’s not as lightweight as one would usually hope from a SBC OS, and it has the usual problems that apt has, but it general, it works. It has the firmware stuff ready, so no hassle with that. It has device trees set up in a generally-usable way from the get go, etc.

I didn’t go that route myself and spent couple of days trying to get hardware acceleration to work where I wanted with the VideoCore chip, after which I gave up. VideoCore just isn’t that well supported by the general software stacks, but this was a year or so ago, so it might’ve improved.

Also note that this is all RPi4 specific. Older RPis work quite well.

RPi uses a lot of software hacks to get its low-cost hardware running. It is certainly doable on other distros, but using anything but the official ones on RPi is asking for trouble, and you better know how to deal with device trees, etc.

If you want SBC that is more standard-compliant and has better mainline driver support you should look at e.g. Pine64’s SBCs, such as RockPro64.