home tags events about login
one honk maybe more

benjojo posted 07 Feb 2024 11:13 +0000

I sometimes wonder, since gtlds are not permanent fixtures (they are sort of subscription payments to ICANN), and a lot of people are seemingly removing their delegations now, presumably to save money, are we going to hit the point where URLify function is not gonna have any idea what is currently a fully qualified host name and what is currently not?

Will anything remember the fact that comcast was once a TLD?

benjojo replied 07 Feb 2024 12:53 +0000
in reply to: https://social.spheron.one/users/edward/statuses/111890223416729238

@edward oh I think it's pretty abysmal. I know NTT uses their gTLD (But at least I know from anecdotal data that their employee's still use their older emails rather than the gTLD one)

(I wrote a bit about this in 2018 when Sony let go of a couple of their gTLD's)[https://blog.benjojo.co.uk/post/the-death-of-a-tld] and it seems that sometimes it's used for email, but not much else.

In the case of comcast, they had:

. nic.comcast
. whois.nic.comcast

and that is basically it...

drscriptt@oldbytes.s.. replied 08 Feb 2024 00:31 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/22Qh86gCwyL193r9k1

@benjojo I hear you but I raise you named-compilezone et al. That produces simple line oriented <record owner name> <record data> that is very safe to pass through awk et al. to get the first column that is the TLDs in the root zone.

And I think about people parsing (read: deserializing) XML, YAML, and JSON, all of which are more complex to parse than tabular data.