We have had and are having discussions about prefix safe:// or the .safenet extension. In this discussion there have been some different opinions although safe:// seems to be most prefered so far. However both sides have the same reason but different conclusions. Both sides want to maximize widespread and fast adoption of safenet.
Since everyone is in such agreement for fast adoption I would like to point out that the surest way to achieve this is to allow present websites to easily have a safe version of their current web prescense. Content is king, and although new services and new sites will emerge as a consecuence of safenet a fast way for widespread adoption is simply that present players on the web will have also a safenet version. This would in itself both market and explain safenet with no other effort, the existing sites would adapt and inform their users of the fact that they now also field a safenet version of themselves.
To get to this very favourable situation we must consider that for a present website the URL they have today is marketing money already spent and brand awareness already paid for. Any existing site today would be much faster to also make a safe version of their site if they can retain their present URL. Any descision that invloves spending money for new brand awareness creation is a way less fast to make for a business than to get extra revenue for something their users already know, money already spent.
Thus we should keep in mind that if a present company that has http://www.service.com today and that can register the adress safe://www.service.com is far more likely to make a safe version fast. If they dont get a safe adress that is the same they will wait far longer before they do a safe vesion of their web prescense. And safenet stands to win alot by getting present web sites to make a safe version, it would help imensely in mass adoption.
I would even suggest we consider to allow the “.” in the safename you can register. This way the site www.news.com could register the safename news.com and then they would have both http://www.news.com and safe://www.news.com
I think that would be an elegant way to allow for safe://www.news.com but still not block the entire .com ending on the entire safenet for just one user. So you should be able to register patrik.com or patrik.se as the safe public id.
If this is techically complicated I dont know, but it seems it would be nothing. Just allow a public id to include the character . and we would get a much faster adaptation from present sites and free marketing for safenet.