I'd argue that OpenBSD would be worthy of that title, too. It is incredibly easy, elegant, and simple. The thoughtfulness that goes into all the base system utilities in OpenBSD is so appreciated.

FreeBSD is kinda somewhere in between Open/NetBSD and Linux in my opinion. Their docs are OK, but the handbook leaves a lot to be desired, and they don't seem to have nearly nice little quality of life utilities that OpenBSD has out of the box.

But me personally, I wouldn't ever connect any of these devices to my network.

They changed their pricing plans several years back, but kept me on the grandfathered pricing, which was very reasonable. Then earlier this year, they more than doubled my annual price, at which point I felt it was no longer worth it. At a certain point, e-mail is e-mail.

For those who just want simple IMAP e-mail hosting, I can recommend mxroute.com and purelymail.com - I've used both, and both work well, and are very reasonably priced. The owner of mxroute.com can be a bit abrasive to uh, put it politely, but to his credit he is very dedicated and responsive. The community surrounding purelymail.com is also responsive and helpful.

I'd encourage everyone to take it a step further and self-host your own IMAP server. Doing this is very simple; use a script like getmail[1] to pull your new messages from your e-mail host and deliver them to your local IMAP server. If you have a VPN set up on your phone and laptops, you can access your e-mail everywhere. Been doing this for years, and it has been wonderful knowing that I have full sovereignty over my entire e-mail history.

[1] https://getmail6.org/

That said, I am glad to see them focusing their efforts on something useful, like laptop compatibility. Regardless, this is a really dumb post. 10 minutes a day is not "daily driving."

Radio Paradise [1] and Radio Swiss Pop/Jazz/Classic [2] are two great ad-free ways to discover new music. There are probably tons of others out there.

[1] https://www.radioparadise.com/ [2] https://www.radioswisspop.ch/en

There was a palpable sense of nearly unlimited potential for a brighter future, powered by technology.

As someone who experienced those decades, present day feels like a dystopia in comparison.

To put it very simply, radios communicate with a central Key Management Facility (KMF) using a special key (UKEK, Unique Key Encryption Key) to securely transport the new key material. There's more to it than that, of course, but these features are heavily used by the feds and also by larger state and local systems -- because manually re-keying each radio is a huge pain.

Using DNS to resolve everything solves part of the problem, but firewall rules are another issue. The router would need to have the capability to update everything dynamically when the prefix changes. I think this in the works for pfSense, but I'm not sure if its actually supported yet. It looks like you might have to mess around with some 3rd-party script to make it work.

I guess I'm just generally disappointed that the whole process seems unnecessarily messy. I don't have a v6-compatible ISP right now anyway. I was thinking about trying a tunnel, but I'm not seeing the benefit in it right now.

When I was reading up on everything, I also learned that your router can request a bigger prefix, but I ran across several posts from various folks stating they could only get a /64 from Comcast no matter what they tried, so I'm not sure how universally supported DHCPv6-PD requests are.

So I started digging in, and there's definitely a lot to like.

But I see two big problems that are showstoppers in my opinion, at least for my home network (not even considering the fact that very few residential ISPs even support v6 at this point):

1. Generally speaking, the IPs of your LAN are based on the prefix assigned by the ISP. Most residential ISPs don't offer static prefixes. This means that every time your prefix changes, the IPs of all your devices on your LAN change. Seems like this "feature" was developed in a more idealistic era when people probably thought everyone would be getting static IPv6 addresses, since shortages would never be an issue. Unfortuantely, they failed to foresee the fact that most major ISPs are terrible, greedy organizations that either outright refuse to offer static assignments, or continue treating them as if they were scarce IPv4 resources, charging a premium or requiring business-class service to even get them.

2. The ISPs that do support v6, like Comcast/Xfinity in the USA, are only allocating one /64 prefix. This means you can only have one subnet (VLAN) on your LAN! Why are they being so stingy?

I would love to migrate to IPv6, but these two issues alone make it feel like a clown show for home users.

I personally think it is absurd that the ISPs that do actually support IPv6 are being so difficult and stingy about assigning static v6 prefixes.

Also, I hope this site doesn't disappear if/when the rather unpredictable .tk TLD operator decides to do something dumb.

And we can't talk about music streaming on the Internet without mentioning one of the originals -- https://somafm.com -- still going strong.

I support both of these stations because their "business model" is so refreshing, very much in the spirit of the "Old Internet," which I miss dearly.