Scott Wilson
Chilly 
🛡️ 
@scottwilson
Securely encoded with base64
GarretSidzaka
cR0w 
@scottwilson Yo what's your
@catte?@cR0w Ooh, my first friend!
@[email protected] is my handle@scottwilson LMAO
Epic Null@cR0w @scottwilson We should make .shitpost a proper TLD
Jason Parker (he/they)@Epic_Null @cR0w @scottwilson I cannot afford the domain registration fees I'd be paying after that.
Crazypedia won't Comply@north @Epic_Null @cR0w @scottwilson We don't even need to go through "official channels". We can just start standing up DNS servers and routing traffic. 🤪
@cR0w @north @Crazypedia @scottwilson @quad9dns @neurovagrant I do have this problem when trying to think up my ideal system.
We have a pretty well designed distribution system for centralized DNS. It comes with a lot of benefits, but the downside is that it's a centralized authority making decisions for all TLDs, with decentralized adherence to this authority.
In my mind, a TLD should naturally reference the autority upon which all subdomains are regestered. That is to say, it shouldn't be One Group that decides who TLDs belong to, but rather TLDs should almost be granted to the authority by the client.
If I want .crow to spawn from cR0w's name resolution servers, then that should be my choice.
@north @Crazypedia @cR0w @scottwilson @quad9dns I would like to propose a secondary Domain Name standard if we do something like this.
A good primary and easy differentiator that I could come up with is comma seperated domains. Having the secondary system use commas has the side effect of being able to build resolvers that can automatically detect and use the correct name format.