Discussion: safe: or safe:// protocol versus .safenet domain

As I noted above, there was a few things that got me thinking about it, but it was centered around trying to increase adoption and consistency of use.

That’s the question. It’s certainly looking like I misjudged the feeling around safenet. But it’s a useful conversation to have. (I should probably not have updated the OP until this discussion was had, so apologies for that. It was by no means intended as a ‘final’ switch. Just an update on where I was leaning after the QnA.)


This isn’t quite the point I was trying to make. I think we should be aiming SAFEr Browser to be a user’s main browser (for clearnet or SAFE). Switching back and forth might be a pain and a barrier to adoption. And the more common features there, the more accessible it would be.

But yeh, this could be putting the cart before the horse. It’s clear there’s a lot of passion for safe:. Adding in useful browser functionality can always be done at a later date.

5 Likes