WebPARSEC [inspired by SAFE-VFS and WebTorrent]

To the best of my understanding, and among many other things, SAFE-VFS allows for two very nifty functions:

#1 - the ability to mount a SafeNet location as a local drive
#2 - the ability to mount a local directory as a safe://my-website.ext

The latter has some interesting implications that has inspired my idea.

If you were to mount /var/www as safe://my-website.ext, this would make a website simultaneously accessible from http://my-website.ext and safe://my-website.ext. For static html websites this would be no issue. For “regular internet functionality” such as PHP or anything that /var/www can deliver, it still should be no issue: seeing as the Safe Web Browser can read http and https every bit as well as the safe:// url syntax. It is the inability for the regular Internet to access any functions requiring safe:// that provides a problem, or rather: AN OPPORTUNITY.

As many of you already know, the beauty of WebTorrent is that it can allow users of a specific website to share their bandwidth with each other. So if for example a bunch of people are simultaneously watching a video on BitChute, everyone currently watching that video is sharing their bandwidth to minimize load on the server, and to maximize bandwidth efficiency for everyone watching. It is a win / win situation. The end user is not required to download or install any software for this to happen.

Now lets take the WebTorrent concept and use it to turn the before mentioned problem into the before mentioned opportunity.

WebPARSEC would act similarly in providing the following functions:

#1 - WebPARSEC would allow for a gateway (however robust or limited) to SafeNet functions for regular Internet users outside of SafeNet
#2 - WebPARSEC would allow regular Internet users to act as temporary SafeNet nodes, sharing their bandwidth with SafeNet as a whole: for as long as they were using the website in question.
#3 - WebPARSEC would allow the regular Internet user to act as a “Mini-Vault” that allows their web cache to store and deliver content chunks to SafeNet users that are simultaneously accessing the site from the SafeNet side of the site.

The regular Internet side of the website would display various details, descriptions and help menus that would explain what is going on and would elaborate on the details of the benefits of joining SafeNet.

Therefore, WebPARSEC would provide the following advantages:

#1 - the soft-sell marketing of SafeNet through positive incentive (plus the fact that SafeNet is free to join doesn’t exactly discourage anyone)
#2 - regular Internet users would be able to provide their bandwidth and resources to SafeNet even if they don’t join, by virtue of simply using a WebPARSEC enabled website


Sorry, but this is not supported. I don’t think it is feasible. You can upload a local directory and publish it as safe://my-website.ext though

1 Like

If I’m understanding his thought process right, if you mounted the save drive as your http web route, your safe content would be shown on http as well. Giving a (albeit static) mirror of your safe site on the clear web.

Edit: looking at it again, it is phrased as you interpreted it. Maybe he can clarify.


WebTorrent sounds interesting and I’ll be looking into it to try and understand this idea better. Does anyone have any useful reference links?


I think it would be feasible if the machine was also a vault. I can understand why it would not be feasible if the machine was not a vault. But if the machine was a vault, then it could upload the directory to itself.

We must keep in mind that not all feature ideas that people come up with are going to be universally supported by all SafeNet users. Some features absolutely will have certain minimum requirements. In this case, being a vault would be a minimum requirement. I personally think that running a safe://my-website.ext should REQUIRE being a vault, until the network is large enough.

This is just the same solution - uploading - a vault can’t bypass the way the network does this just because its a vault. So there would need to be a user account, and the upload would cost PUTS (so just like uploading any website to SAFE).


Well, I did provide one useful reference link. BitChute is a site that uses the WebTorrent technology. Minds is another.

But if you need more direct examples in the form of specific videos and the direct link to the WebTorrent project itself:

An example of a BitChute video which uses the WebTorrent technology.

An example of a Minds video that uses the WebTorrent technology.

WebTorrent project, FAQ direct link.

Hope that helps! :slight_smile:

1 Like

Well, thats alright. Just because it will have to work a particular way, doesn’t mean its not workable at all. Just means it will have to work however it has to work.