The vanity .tld system was a terrible idea and ICANN should be beaten with barracuda for allowing it. Nobody needed a TLD for '.boats' or '.cheese'
Conversation
Notices
-
Embed this notice
Matt Linton :donor: (amuse@infosec.exchange)'s status on Thursday, 16-Nov-2023 02:57:11 JST Matt Linton :donor: -
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 16-Nov-2023 02:57:06 JST Ryan Castellucci :nonbinary_flag: @amuse @lcamtuf I believe that was Postel writing about TCP whilst failing to realize what a mess he was setting us all up for.
-
Embed this notice
lcamtuf :verified: :verified: :verified: (lcamtuf@infosec.exchange)'s status on Thursday, 16-Nov-2023 02:57:10 JST lcamtuf :verified: :verified: :verified: @amuse What? I personally find the system too constraining and hope we move to the next logical step: https:// replaced with vanity protocols
-
Embed this notice
Matt Linton :donor: (amuse@infosec.exchange)'s status on Thursday, 16-Nov-2023 02:57:10 JST Matt Linton :donor: @lcamtuf Reminds me of the original SMTP RFC guidelines; "You should be strict about the RFC while sending, but graceful when receiving".
But look where THAT got us.
-
Embed this notice
Matt Linton :donor: (amuse@infosec.exchange)'s status on Thursday, 16-Nov-2023 03:41:51 JST Matt Linton :donor: @ryanc @lcamtuf You're right! I confuse so many early RFCs and the listserv discussions about them sometimes. Especially from Jon, who was particularly prolific :D
-
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 16-Nov-2023 03:57:46 JST Ryan Castellucci :nonbinary_flag: @amuse @lcamtuf it was on my mind from recently realizing my thoughts on that adge have gone from "this is enlightened" to "this is a dumpster fire" to "haha filters go brrrr".
-
Embed this notice
Matt Linton :donor: (amuse@infosec.exchange)'s status on Thursday, 16-Nov-2023 03:59:11 JST Matt Linton :donor:
-
Embed this notice