Live data from Hacker News

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

hccf.onmy.cloud

251–260 of 410 posts

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

#251
post #167

Earlier quoted context omitted.

How much is the reduced fee then? As I understand it's somewhere between 75-85% less, which is still a lot of money. Also, who is paying for the reduced fee, administrative and infra costs? And have you actually submitted gTLD application, or are you trying to crowdfund? Unclear to me.

The fee will fall on us to pay and the gTLD application window is open and our application is in progress. Yes we are crowdfunding (there is a donation link on our website and in the pamphlet) while also actively seeking partners to sponsor us.

If anybody is asking you "are you trying to crowdfund" and your answer is "yes,", you've clearly failed at conversion, marketing and UX design.

90+% of people who would be willing to sponsor this stuff will go "hmm, I wonder where they've taken their money from, not us I guess." Not everybody reads comments, even fewer post ones of their own.

Being on the front of HN is a great opportunity, I'm afraid you haven't used yours as well as you possibly could.

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

#252
post #172

Earlier quoted context omitted.

I had a similar class where they threatened to fail us if we didn't use Dreamweaver and instead wrote our own html.

Dreamweaver was cool as a beginner because it took a lot of the troublesome parts out of the equation. But it did end up being more of a hindrance than a benefit the further you went in.

What were these "troublesome parts"? The whole point of HTML's design is that it's incredibly easy for a human to write correctly.

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

#253

https://hccf.onmy.cloud/wp-content/uploads/2026/06/dot-self.... > Everyone entitled to a subdomain at no cost How are you going to pay for the (substantial) cost of running a TLD without registration fee revenue? Is this a loss leader for other services? Are you operating on a 100% donation model? > No parking, squatting, or reselling How do you plan to tell the difference between a parked/squatted domain and one in…

Might be a public service? I guess many countries already had such a thing with running cost several order higher than such a thing as a TLD, operating for centuries now.

Countries have the loop of "taxpayers pay government -> government funds service -> service benefits taxpayers." You can't do that if you offer the service to the general internet.

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

#254
post #244

The "one free domain per person" isn't the interesting part really - that will be hard to police unless domain name is a function of ID proof (avoids squatting). 0) The actual intersting part of a new TLD can be growing reputation by post-facto taking away a domain without recourse in case of squatting. Instead of adversarial takedowns (which produce false positives as noted), let anyone challenge an inactive domain…

The much simpler way to avoid squatting is to make .com domains cost $200 a year. This will instantly end the vast majority of domain squatting on the .com TLD and if people can easily get the .com they need for their business then the other TLDs are not going to have much squatting activity.

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

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

#255
post #204

Earlier quoted context omitted.

.io is (British) Indian Ocean (Territory).

I always thought these TLDs were a flight risk to be used in any serious capacity. What if the random state decides you/your business are in violation of [whatever] and kick you off?

[deleted]

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

#257

Earlier quoted context omitted.

I am probably missing something, but how DNS TXT updates can be made difficult to automate?

We can get creative. quick ideas: Send it by printed post. pass it around people to people. an email needs to be added in with some process, and can only get one TXT update value a week. Many ways of adding friction to obtaining the updatable value - which a human owning a domain would be happy to do, but a squatter would not want to.

> Send it by printed post

that's how one of my local companies tries to force clients in. They removed auth code from their web panels and introduced complex snail-mail procedure.

That was clear signal to run, but it took me 6 months to do just the domain transfer.

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

#258

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.

I still have a .tk domain, paid since 2008, because it was the only one with my surname available.

Haven’t had much issues but surely if could go back and i’d pick a different tld.

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

#259
post #244

Earlier quoted context omitted.

The much simpler way to avoid squatting is to make .com domains cost $200 a year. This will instantly end the vast majority of domain squatting on the .com TLD and if people can easily get the .com they need for their business then the other TLDs are not going to have much squatting activity.

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.

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

#260

Earlier quoted context omitted.

Dreamweaver was cool as a beginner because it took a lot of the troublesome parts out of the equation. But it did end up being more of a hindrance than a benefit the further you went in.

What were these "troublesome parts"? The whole point of HTML's design is that it's incredibly easy for a human to write correctly.

There was a ton of... not exactly footguns, just things to keep in mind if you’ve wanted your site to work as you intended in all browsers. The webcompat nowadays is way better now.

That said, personally I’ve never understood Dreamweaver either. By the time I tried it, I’ve already got used to Notepad++ and writing HTML by hand, so I’ve just treated it as another text editor... and IIRC it just felt way more laggy than Notepad++, with a browser preview panel that took half of my 4:3 display. Maybe I’d discover some cool features if I’ve spent some more time in it? I dunno.

Post reply on HN