Earlier quoted context omitted.
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 use…
.self: A new top-level domain designed to support self-hosting
261–270 of 410 posts
Re: .self: A new top-level domain designed to support self-hosting
#262Earlier 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.
Re: .self: A new top-level domain designed to support self-hosting
#263Earlier quoted context omitted.
Can you talk more about RISC Zero? Does it require a TEE of some sort? I had trouble finding a quality mid-detail spec of how it works; lots of marketing materials basically.
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…
Re: .self: A new top-level domain designed to support self-hosting
#264Earlier quoted context omitted.
My guess is by using ID verification similar to how I do it on https://onlyhumanhub.com/
So you have just built a wrapper around https://passportreader.app/ , which itself is reading NFC enabled ID/passports from specific countries. The coverage map is here: https://passportreader.app/coverage . Might be good to know that even in the US this approach would only work for ~50% of people, since a lot of people don't have passports. In most countries this does not work at all, since they don't issue NFC enab…
Oh, cool! Russia is not on the list. Another service that excludes me just becasue I got lucky with the colour of my (NFC-enabled, biometric) passport.
On a less bitter note, I don’t think it’s that hard to build biometric passport validation. Face matching would be another thing, but for unregulated industries I don’t think you’ll need that, so why not grab some library from GitHub and be in control of the whole process? (You would still need to handle people without biometric passports somehow, of course.)
Re: .self: A new top-level domain designed to support self-hosting
#265The "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…
I dislike the term “domain squatting”. It should be called “domain scalping”.
Re: .self: A new top-level domain designed to support self-hosting
#266Earlier quoted context omitted.
Those were the days indeed. A big part for me is probably because I was a teen at the time with little responsibility, but getting to be a part of the wild west days of the internet was a magical experience.
Magical indeed! I once mailed $70 cash (multiple months of allowance) to someone to code a MVP of something I wanted to build. They ripped me off and disappeared. And… that’s when I decided I needed to learn to code!
Re: .self: A new top-level domain designed to support self-hosting
#267I remember that the local service provider in the 1990s offered free homepages for all customers. Over the years this, strangely enough, disappeared completely; still not sure why, but it was harder to get hosting. It's still possible today, even for free, but it is more of a hassl and harder to do so than what I remember in the late 1990s early 2000s. I actually think every citizen should automatically get a free homepage etc..., if they want to (should be guaranteed to be an option, never mandatory of course; and I also think it should be a human right, together with access to information. Some countries perma-ban people who "violated" something e. g. downloaded copyrighted material, that also needs to be eliminated and states that do so should be called brutal dictatorships.)
Re: .self: A new top-level domain designed to support self-hosting
#268Earlier quoted context omitted.
And you needed a gTLD for this task why?
We don't necessarily, however there are many benefits for doing so. We could simply purchase a domain and then build our initiative beneath it but then everything we do would be beneath that domain, meaning there would be two dots in what is our effective TLD. That would also mean we are a bit beholden to whichever TLD we are beneath and also whichever registrar we purchased our domain from. With the services we hope…
Re: .self: A new top-level domain designed to support self-hosting
#269Earlier quoted context omitted.
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
#270Remember 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.
The schools admins told me he had tenure so there was nothing I could do.
Didn’t take me a whole year before I switched majors.