.self: A new top-level domain designed to support self-hosting
31–40 of 410 posts
Re: .self: A new top-level domain designed to support self-hosting
#32Earlier quoted context omitted.
The only mistake was not opening the root namespace altogether. It’s just a money grab.
The only mistake was not putting all US domains under .us, now the US has an an exorbitant privilege to print and enforce rules on new TLDs.
Re: .self: A new top-level domain designed to support self-hosting
#33Re: .self: A new top-level domain designed to support self-hosting
#34Re: .self: A new top-level domain designed to support self-hosting
#35I 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.
Re: .self: A new top-level domain designed to support self-hosting
#36[flagged]
Re: .self: A new top-level domain designed to support self-hosting
#37Site errored out and gave me three different error messages as I reloaded. I guess it's self-hosted on something underpowered, and dynamic where static would do the job?
Re: .self: A new top-level domain designed to support self-hosting
#38Re: .self: A new top-level domain designed to support self-hosting
#39Hold up...why isn't .self listed here: https://www.iana.org/domains/root/db Is this just an idea at this point, or some kind of "you have to use our DNS to resolve .self domains" scheme - ?
This is an idea at this point, the next round of gTLD applications is currently open and we are in the process of applying and we are trying to garner support!
Cloudflare offers this now (their Pay to Crawl service) but its not geared towards every human getting paid for their content. As of today Facebook and other social media platforms profit from our content....not us!
Re: .self: A new top-level domain designed to support self-hosting
#40Will there be any assurance that renewal prices will remain fairly stable, rather than being significantly raised after customers grow attached to their domains (a practice that seems to be common with new gTLDs)?