Live data from Hacker News

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

hccf.onmy.cloud

281–290 of 410 posts

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

#281

Do the people who are promoting this know that it costs approx. $227,000 to apply for a new gTLD with ICANN?

The Applicant Support Programme makes it significantly cheaper (if they qualify).

See https://newgtldprogram.icann.org/en/application-rounds/round...

And https://www.kickstarter.com/projects/dotmeow/meow-next-round...

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

#282
post #216

Earlier quoted context omitted.

What if an elephant steps on the power cable to the server room?

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.

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

#284
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.

I left community college after a week because my "computer" teacher required us to change our monitors to 640x480 and print out ever step that we completed in things like Notepad or Configuring the Desktop and then every day we'd punch it out and would add it to a three ring binder of all the things we've done.

Full Color.

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

#285
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.

I assume this was at a highschool and not at university? My IT teacher in highschool was the chemistry teacher, because.. he knew how to use Word, I guess?

He knew we were computer nerds so didn't really care about teaching us (we knew more than him anyway). And we didn't mind that he just sat there drinking coffee and reading a book, as it meant we could just play videogames for an hour. Good times.

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

#286
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.

How does this lend itself to self-hosting then? I think few people will pay that much to self host.

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

#287
post #95

Earlier quoted context omitted.

.zip was especially egregious. No one should have allowed that to happen.

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.

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

#288

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…

.id.au already has some similar requirements for associating a domain with a real world (human) identity: https://www.auda.org.au/au-domain-names/the-different-au-dom...

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

#289

Earlier quoted context omitted.

zkVMs (of which RISC Zero is one example) do not require a TEE. That's the whole point: the privacy properties come out of the math. Basically, nowadays, once you and I can agree on the text of a program, you can run the program on your private inputs and produce a number that proves to me that you actually ran this specific program and not some other. For example, age verification: I can run a program that takes a s…

What does require a trusted computing platform, however, is ensuring that the same program isn't being executed millions of times per second to send millions of different ZKPs to different parties. ID verification is not enough, you also need some way to prevent one malicious user from re-selling the same ID to millions of others. Without ZKPs, you know what document the user is trying to sign up with, so you can rat…

Yeah, this goes back to the blind spot we technical people have: Solve people/social issues with technological enforcement.
Post reply on HN