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

I understand why the TLD approach is being chosen, but I’m not happy about it at all. I’m mostly afraid we’ll forever be stuck with it as TLD links are used and stored everywhere in SAFE apps and people’s minds.

Why not just bundle a rebranded Firefox (including required plugins) with the installer? If people are adventurous enough to switch from their current solutions to SAFE, using a different browser to visit SAFE web content isn’t that big an ask. Especially if it’s included in the installation.

A single dedicated browser has many security benefits as well. Using the same browser for both the regular web and the SAFE web practically guarantees cross-contamination and security issues. Simple example: Javascript code in a SAFE website that creates a direct connection with a regular server, de-anonymising the visitor. This can be solved easily in a dedicated browser (disable any communication other than with the SAFE launcher service). In a regular browser, especially restricted ones, this may not be solveable at all.

I fear the virtually guaranteed security holes with non-specialised browsers are going to hamper SAFE adoption’s a lot more than the non-optional usage of a dedicated browser.

13 Likes