4 ms·
I'm not keen on legally mandating the use of a particular domain extension, unless that extension is managed by a non-profit. Some of the newly-added TLDs have
by profmonocle 7y ago
I'm not keen on legally mandating the use of a particular domain extension, unless that extension is managed by a non-profit. Some of the newly-added TLDs have exorbitant annual fees, and if businesses were legally required to use them they could charge whatever they pleased.
Plus, you'd have a collision problem. What if one company has foobar.com and another has foobar.net, and they both collect data? (Imagine they're in completely different industries and the term itself is fairly generic, so there's no possibility of a trademark dispute.) They can't both get the ".delete" version of their second-level label.
(I realize I'm probably overthinking this.)
- CydeWeys 7y agoYou'd have to create the real TLDs as SLDs on .delete, and then the way to make a .delete domain would simply be to append .delete to the existing FQDN. So you'd thus have foobar.com.delete and foobar.net.delete, no collisions. Not saying it's great, but it'd work.
- DrKabab 7y agoInstead you could just have delete.foobar.com and delete.foobar.net instead, wouldn't need buying a new pricy domain name...
- C14L 7y agoOr simply standardize a mandatory "example.com/delete-all-my-data" path on the same domain.