SAFE URL: use a real internet domain such as safenetwork.net

[happybeing]

The following point has not been considered so far in this topic:

@TylerAbeoJordan

EDIT again: I must partially retract my view that “SAFE:” addresses will not end up being sent out to meta-data collectors (if an unrecognized protocol) … it turns out that most browsers by default now dump unrecognized strings to search engines!!! Holy moly, what a security breach. Anyway, this can be disabled (and should be!)

This means we need to reconsider the security implications of using a URL that the browser - without a plugin - can in fact interpret, because it means that rather than sending a SAFE URL to a search engine, a browser would visit the website we administer instead.

Anyway, as I’ve suggested in the following post, I suggest that we revisit this discussion when we’ve got a better idea of the different options.

SAFE URL: "safe://" cross browser support revisited!

Important point, I hadn’t thought of this. We need to sit down and consider the implications of different methods of browser support and their implications. I think it’s just too valuable for ease of use and mass adoption to not support existing browsers, and I can’t see how we can mitigate this - except to a small degree, by ensuring that all SAFE URLs behave like a normal URL when using a browser that doesn’t understand them! I refer of course to the following suggestion (…