As some of you already know, @frabrunelle @erick and me are behind the Montréal POD. At our first meet up, we brainstormed and decided to build a browser extension that will allow normal users to access webpages hosted on the SAFE network.
We found multiple ways to achieve that vague goal. Three were retained, and we’d like to ask you your opinion on them.
1 . Create a browser extension that would generate a config file for a request to the SAFE Network. The extension would then call an executable (that is able to send requests to the SAFE Network) and pass the config file as an extension. This is what XTTP and MeshedSites are doing.
Pros: Light extension.
Cons: Need a MaidSafe installation from the User (or at least a light version) and ask him where it resides, is more prone to slowness, we would surely need to build the executable.
2 . Create a browser extension that would redirect (in background) SAFE Network requests to a local proxy. This proxy will then treat and send the request to the SAFE Network. The proxy would need to be a full featured MaidSafe package, like what I2P does.
Pros: Really simple extension, easy to port to other browsers.
Cons: Need to install a packaged version of MaidSafe containing the local proxy. We would need the build the proxy and package it.
3 . Create a layer on top of the MaidSafe librairies in Node.js, using node-gyp to integrate the MaidSafe C++ librairies inside the layer. This layer could then be integrated in a (heavy) extension.
Pros: The layer (or Bridge, as we call it) could help other developers to start their projects, The User doesn’t need to install anything else, Easier to integrate the MaidSafe APIs.
Cons: The extension would surely be heavier than most extensions, it would also need to incorporate executables for all platforms (if I understood node-gyp correctly).
That’s about it for now! We’re eager to hear you out!