NixOS gang, you here?

No? Guess I’m here alone. Meme checks out.

Here you go. https://theycantalk.com/post/667874745661915137/predicament

.localhost is already reserved for the loopback, per RFC 2606, but I agree with you in general. A small network shouldn’t have to have a $10-15/year fee to be compliant if they don’t want to use a domain outside their network.

As other posters have mentioned, .lan .home .corp and such are so widely used that ICANN can’t even sell them without causing a technical nightmare.

Yes, you’re right, RFC 6762 proposes reserving .local for mDNS. I was not aware of this until you brought it up, hence the dangers of using using TLDs not specifically designated for internal use.

Very few as this ruling would reserve .internal for local DNS only and forbid it at the global level. This is ICANN’s solution to people picking random .lan .local .internal for internal uses. You’ll be able to safely use .internal and it will never resolve to an address outside your network.

I find myself commenting more frequently on Lemmy as well. I attribute it to there being less comments in general so less has already been said. By the time a post shows my reddit feed there’s already hundreds of comments and the discussion is already pretty well laid out. At that point I don’t really have anything meaningful to add.

Has someone been reading https://wtfhappenedin1971.com/?

It does exist, see qbitorrent and similar apps. Torrents already fill the usecase you’ve defined: decentralized sharing of arbitrary files. The main problems being the central exchange and the need for seeders.

The bigger the central exchange (torrent tracker) the more susceptible you are to both internal and external threats, but you need to be big because bigger means more seeders and more content.

Considering how thick that ice is and how fast it’s moving, this is actually pretty terrifying.

It’s really cool to see in real time an example of how a glacier can erode the terrain though.