this post was submitted on 31 Jan 2024
167 points (97.7% liked)

Selfhosted

40006 readers
552 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] 23 points 9 months ago (1 children)

Huh, I've seen .local used for this quite a bit and only just now realised that it's meant for something else.

I've also seen .corp 🤮

[–] [email protected] 21 points 9 months ago (2 children)

And .home.

Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it's just the latest addition to the list of possible TLDs and confusion continues.

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago)

It's such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They're safe by ICANN policy, but unsanctioned.

.home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I've used . internal for lab testing stuff for ages, so this is extra good news for me I guess.

Really I wish they'd have just reserved the most common ones rather than getting caught in some bureaucratic black hole.

[–] [email protected] 28 points 9 months ago (1 children)
[–] [email protected] 14 points 9 months ago* (last edited 9 months ago) (1 children)
[–] [email protected] 11 points 9 months ago (1 children)

That one is absolutely abhorrent because I know as a fact my parents would easily fall for a .zip domain leading to a virus infested site thinking it's actually them getting a zip file because they don't know better. At least the first few times they'd fall for it.

[–] [email protected] -3 points 9 months ago* (last edited 9 months ago) (2 children)

How would you know?

Edit: Sorry I meant how would you yourself know whether it's a file or domain

[–] [email protected] 4 points 9 months ago

The last time I talked to my mom about a zip file, she didn't even fully understand what a zip file is. That's how I know my mom would get confused.

My dad, he's better since he has and uses a laptop, so he knows more than my mom, but he's still not the brightest when he has CCleaner and malwarebytes installed simultaneously on his laptop. Hell, back around 2018-2019 he was extremely stubborn about me trying to fix the family computer that had a password that I didn't know on it. I just wanted to uninstall some bad programs (don't remember which ones) and my dad was getting super anal about it. I have no doubt if he did accidentally click on a .zip web link, we'd never know because he'd be too stubborn to admit it.

[–] [email protected] 8 points 9 months ago

Because they’re his parents, not yours