3 ms·
> complicates validation and security for developers No? If this broke things for you then I've got very bad news about how broken those things already were.
by tialaramex 6y ago
> complicates validation and security for developers
No? If this broke things for you then I've got very bad news about how broken those things already were.
Only textual exact matches of A-labels work for figuring out if names are the same. Guessing that if parts of the name seem kinda similar maybe that's enough just introduces endless weird security bugs.
And the new TLDs didn't change that, example.com isn't example.org and example.photos isn't example.pictures or example.snaps or example.selfie
If you think you need "effective TLDs" then you actually wanted the Public Suffix List, and the reason that's what you wanted begins decades ago in several ccTLDs and isn't the fault of this cash grab at all. Remember to thank Mozilla again while you're there.
- quotemstr 6y agoIt's not technical breakage that's the problem: it's the mental breakage. This proliferation of TLDs confuses users and makes domain names less recognizable, all for no benefit to anyone but ICANN.