We should probably just bring back Geocities at this point.
Neocities exists and you are welcome to it :)
.self: A new top-level domain designed to support self-hosting
211–220 of 410 posts
Re: .self: A new top-level domain designed to support self-hosting
#212ICANN and its consequences have been a disaster for the internet namespace.
This is just a fact. It's a ponzi scheme.
Re: .self: A new top-level domain designed to support self-hosting
#213Earlier 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.)
Re: .self: A new top-level domain designed to support self-hosting
#214Re: .self: A new top-level domain designed to support self-hosting
#215If this is supposed to be human-centered, why isn't it .human? I assume there will be many agents with their own ".self" domains that have very little human oversight.
Re: .self: A new top-level domain designed to support self-hosting
#216Earlier 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?
Re: .self: A new top-level domain designed to support self-hosting
#217Earlier 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.)
What do you have against Moldova?
Re: .self: A new top-level domain designed to support self-hosting
#218Re: .self: A new top-level domain designed to support self-hosting
#219Earlier quoted context omitted.
Sounds like a bad domain for self hosting. You have to update txt records randomly and your domain can be taken for whatever reason. Whatever value you build goes away if you are inactive. You cannot transfer ownership killing any value you added.
Hence the "in the first year or two". Some more human effort to showcase proof early on, then the domain is solidified for you like iwth any other registrar. This is something like captcha/bcrypt - a single instance isn't a burden, but doing it at scale is costly. > You cannot transfer ownership killing any value you added I think this is by design. The domain should be for personal use - hence free.