I could imagine that the web-server could be able to have data pre-processing plugins and post-processing javascript ‘plugins’, allowing for different functionality within the browser and possibly subsequent modification/processing of data. Perhaps such would give the flexibility that @smacz desires?
I suppose there would be a security issue, but using something like php with the server would allow the use of some traditional web technology … although I don’t know if there would be any advantage to that and the complexity goes up quite a bit. Anyway, fun things to contemplate.
EDIT-ADD:
read through your github link …
Though the development and initial configurations are made easier, the user experience might not be great because the
user has to manually click on the prompt to authorise each and every time. An option to persist the authorisation
can be a feature that can be added in future to improve the experience.
Why would the option to persist be added in the future? Is this a difficult thing to do?
I am still not sold on using http in links to safenet data. Even with a custom tld, for browsers not configured to use a proxy for such tld, their browsers will run through traditional insecure routes, thus exposing the user (who may have been given the link) to malicious meta-data collectors.
Why can’t we use protocol handlers for all devices and all browsers? Is it true that mobile device browsers do not support protocol handling?
what about this?: https://lists.macosforge.org/pipermail/webkit-qt/2010-April/000466.html
Being able to use a wide range of tld’s is helpful to categorize the web, whether that web is the existing one or a new one being built in SAFEnet. It is also more recognizable to both web-developers and web-users.
Come use SAFEnet today, where you can have your creativity even more limited than you do with the existing net!
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!)
e.g. with firefox: Search the web from the address bar | Firefox Help
Still this leaves a security hole for most users who do not have a protocol handler for “SAFE:”. I guess for the average person who isn’t security conscience, they will inevitably face the wrath of bad actors collecting data.
Still my argument in favor of “SAFE:” isn’t dead as, for me at least, being able to use any tld I like is a big bonus.