Live data from Hacker News

.self: A new top-level domain designed to support self-hosting

hccf.onmy.cloud

391–400 of 410 posts

Re: .self: A new top-level domain designed to support self-hosting

#391

Remember when the .tk TLD became free 20 years ago ? Every hobbyist took one, then scammers followed, then Facebook and antiviruses started blocking it. I remember publishing a website for a class on my .tk domain, the teacher couldn't open it and I almost got a failing grade because of it.

And then everybody left, yeah, I remember this exactly.

Re: .self: A new top-level domain designed to support self-hosting

#392
post #278

We could fix a lot of this by just making sure .local (which is used in Bonjour/mDNS) could coexist sanely in mixed resolver environments _and_ could support subdomains. I built https://rcarmo.github.io/projects/mdnsbridge to “fix” it for my particular use case, and if it wasn’t for TLS shenanigans and the lack of subdomains, my issues largely went away.

Good to know you're still building your own tools like back in the "old days" :)

Re: .self: A new top-level domain designed to support self-hosting

#393
post #169

Remember when the .tk TLD became free 20 years ago ? Every hobbyist took one, then scammers followed, then Facebook and antiviruses started blocking it. I remember publishing a website for a class on my .tk domain, the teacher couldn't open it and I almost got a failing grade because of it.

A friend almost failed an IT class because his website didn't render at all in IE6. This was during the time of IE9. The teacher just hadn't updated their browser in a long time. I don't get how you get to be an IT teacher without knowing the most basic troubleshooting steps to get assignments to run.

This feels like a good place to reel out my favourite anecdote; community college IT (or for the natives; BTEC), 1998; our programming tutor told us to "ignore the internet" because it's a fad.

Almost 30 years, and every so often I still wonder about where that got him.

Re: .self: A new top-level domain designed to support self-hosting

#394

Earlier quoted context omitted.

I don't get it. How do you handle 10k people wanting, say, garden.com, without a free market?

first served or random from a waitlist are other options.

First come first served is capitalism in disguise. Someone will automate a tool that watches for these and jumps on them, and the person with the most resources, can get a close network connection, etc will "buy" it.

Same with waitlists.

It's impossible to avoid capitalism!

Re: .self: A new top-level domain designed to support self-hosting

#395
post #262

Earlier quoted context omitted.

I never understood Dreamweaver. The first thing it asked me when making a new website was ... what the resolution of my user's screen is? I don't know that!

Its web development software from the 90s/00s, a period when websites were built by first having a designer meticulously mock everything up in Photoshop on a 640x480 canvas (maybe 800x600 or 1024x768 in later days), that mockup would then be handed over to a web developer (hi, that was me) who would take that mockup, slice it up into a billion little images, and then put them in a wildly complex set of nested HTML ta…

This is exactly how I remember my early webdev days. Before Dreamweaver we were using NetObjects Fusion.

Re: .self: A new top-level domain designed to support self-hosting

#396

Earlier quoted context omitted.

We plan to operate a shared mail server than can be used by users of the domain and we will work to ensure it is trusted by imposing usage limits. We will assume that every endpoint in our domain is someone's personal homelab, meaning small-scale use. For large mailing campaigns and newsletters there are plenty of services to choose from that enable those but for just sending personal emails, it should work.

Wait, so self hosting but I don't host my own email? So you guys just want to run your own mailserver and give people custom emails? That sounds like negative utility. That would make hosting an email server on one of your domains harder than hosting it on a .com, so what benefit is this providing?

One of the biggest problems people have when self-hosting their own mail servers is delivery issues because the big email providers don't trust your server. The goal with the shared mail server is to create a server that is trusted by those providers and then making it accessible to users of the .self TLD so they can forward their mail to it and have confidence it will be delivered. It would act only as a relay, users would still self-host their own mailboxes. And nothing would force you to use it.

Re: .self: A new top-level domain designed to support self-hosting

#397

Earlier quoted context omitted.

The owners of `queer.af` thought that AF only meant “as f*ck”, without realizing that AF also happens to the be the ISO 3166 code for a country controlled by the Taliban, who didn’t like their domain name [1]. Brits that had `.eu` domains lost their domains due to Brexit [2] (unless they had some other EEA ties). And if the Chagos deal goes ahead [3] and the British Indian Ocean Territory ceases to exist, then all `.…

Assuming the British/American air base remains on some agreement with the Mauritian government, then the Chagos Islands may remain as a special territory of Mauritius, justifying the continual existence of an ISO 3166 code for it.

Actually, Diego Garcia (the British/American military base) already has it's own ISO 3166-1 alpha-2 code, DG: [1]

It's "Exceptionally reserved" "at the request of International Telecommunication Union (ITU)".

Although my gut feeling is that if the deal happens, Mauritius would probably ask to exceptionally reserve `IO` as well. Still, I'm not sure if I'd risk using a `.io` domain since it's not guaranteed.

[1]: https://www.iso.org/obp/ui/#iso:code:3166:DG

Re: .self: A new top-level domain designed to support self-hosting

#398

Earlier quoted context omitted.

There are three TLDs I block on my computer completely, and all of them are file extensions - .zip, .md, and .mov. (Yes, the domain "readme.md" exists. Fortunately, whoever owns it is not using their power for evil and does not have any webserver there... but I'm not risking it.)

I am SO tired of the Claude docs site getting a rich preview every time anyone mentions “claude.md”. At least it’s registered by Anthropic, but what a terrible decision to allow these TLDs.

To be fair, .md is the ccTLD for Moldova, first set up in 1994[0], ten years before Markdown was even a thing. The ccTLDs use the ISO 3166-1 alpha-2 country codes, defined in 1974 (according to Wikipedia)[1].

Moldova has every right to the ccTLD. It's just that I find that Markdown files can sometimes get auto-linked to the corresponding (and frequently non-existent) domain, which could catch me out if I'm unaware... and I don't even know of any sites using that ccTLD, hence why I block it.

Nothing personal, Moldova.

(.zip and .mov were terrible ideas, though.)

[0] https://www.iana.org/domains/root/db/md.html

[1] https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

Re: .self: A new top-level domain designed to support self-hosting

#400

Earlier quoted context omitted.

Tell me you don't know when a CDN is needed without telling me you don't know when a CDN is needed

> The primary purpose of the Cloudflare DNS Proxy is to act as a reverse proxy that sits between your website visitors and your origin server. When enabled, Cloudflare intercepts incoming web traffic, processes it, and shields your server from direct connections. Maybe you are not up to date on latest trends, but modern CDN purpose is to shield the origin from the public writ large.

That's the marketing pitch of cloudflare, yes. That doesn't mean that it's a good idea, it means that they'd like it to be.
Post reply on HN