SAFEr Browser(s) Proposal

Personally I’m not convinced that we should continue to use .safenet. Sure, it would let us support more browsers (e.g. Chrome), but do we really need to support as many browsers as possible?

I’m pretty sure I would prefer to use safe: (simply because it looks better and makes it clearer that SAFE is a new protocol different from HTTP) even if it means that we can’t support Chrome.

Chrome users could simply download and use the SAFE Browser.

I think we need to have a longer discussion about this. I just created a new topic called Discussion: safe: or safe:// protocol versus .safenet domain.

10 Likes