I am wondering if that could be implemented on the root level of the SAFE Network.
In the “http://” network, we do re-directions to “https://” using a script on Apache Conf, Bind makes the re-direction from ip addresses to names,
Why not do the same sort of thing in the SAFE Network?
You’ll find lots of discussion about this if your search for “safe:” and “safe url”.
Those discussions are largely around the idea of using existing browsers with a SAFE plugin though. Using a SAFE browser changes things, so we could ditch the “.safenet” and just use “safe:”, or ditch both and just use public ids, so when using the SAFE Browser the URL would be “dirvine” for example rather than “http://dirvine.safenet” or “safe:dirvine”. This would though cause problems for people using existing browsers which would still need the “safe:” and/or “.safenet” clues in for the access to be diverted from clearnet to SAFEnetwork.
That is the point. You do not want vulnerabilities. What if someone decides to make ICAAN .safenet service. You’re gonna have bad time telling the difference between clear net, and safenet.
This is best way to be sure you are using safenet service, and only for that service. It will block clearnet scripts.