Video: Developing Dapps for SAFE


Great @jimmyhacksthings.

One thing that could be better communicated is that the SAFE Network has never actually been based on a browser. Previously a fork of the Mozilla, then Beaker and others have been put forward by the dev team as an access platforms. Current version of the SAFE browser is being developed as a means of having a secure experience without leakage to the clear net. Anyone who wants can eventually build whatever browser they want for access, or none at all for access via IOT. Just need to use the network protocols to connect and read/write.

EDIT: No, don’t take it down. Maybe do a follow up on some points, but leave it regardless. Will do much good, either way, I think.


Just so you know the APIs have interfaces to the popular programming languages and of course ‘C’

Yes the IoT interface is very important.

Oh and thanks for the Vid, always good to see these videos and getting an external view on progress.


A plugin for chrome would be ideal way to use the network in my opinion.


Even though the access of the SafeNetwork from ‘clearnet’ browsers through extensions/add-ons sounds like it may be practical and functional to the initial popularization of the SafeNetwork… the fact is that it would undo the security advantages of the unique design of the SafeNetwork.

In short it would be an enormous security risk.
We have enough phishing on the clearnet, let’s keep the SafeNetwork Safe.

This threat is not just hypothetical:


As you can see, it is rampant in the wild.
Allowing SafeNetwork extensions on clearnet browsers would allow traditional ‘hacking’ methods to compromise SAFE users.


Thinking out loud here, it seems like the best way to protect against malicious/fake third-party extensions for SAFE Net (or extension takeovers) would be for MaidSafe to provide and market its own. Otherwise a very convincing-looking fake one will inevitably appear and trick a lot of people. As I understand it though, maintaining an extension is a lot of work, especially across multiple browsers.

We could strongly caution users not to download extensions for SAFE at all, but you know some people will be tempted by the convenience, or see it as a new form of VPN service. Then they’ll get pwned. Again, just my opinion.


Hypothetically, how would a Safenet user access from an Apple iOS device in the event the Safe browser is removed from the app store? My best idea to date is to reimplement the Safe browser for distribution from any ordinary website as a simple Web Assembly file that can be loaded with Safari on the frontend.


Did a quite Google search to see if anything popped up on this and found this -

I found a bunch of videos on Youtube about getting around it also.



‌‌ ‌‌ ‌‌ ‌‌ ‌‌


As I didn’t qualify my statement with “sans jumping through technical hoops” you’re correct. That option is however unrealistic for most and I don’t think it can be considered a solution.


I think that the demography of users who would even think about jailbreaking as an option, might have already switched to the Android ecosystem by now.


Which underscores my point further that jailbreaking shouldn’t be seen as a solution.