this post was submitted on 08 Aug 2024
498 points (99.0% liked)

Selfhosted

40330 readers
407 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 34 points 3 months ago (18 children)

Why do I care what ICANN says I can do on my own network? It's my network, I do what I want.

[–] [email protected] 20 points 3 months ago (1 children)

Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won't go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It's the URI equivalent of 192.168.0.0/16.

[–] [email protected] 5 points 3 months ago

Interesting that you should use ".local" as an example, as that one's extra special, aka Multicast DNS

load more comments (16 replies)