SAFE-VFS (Virtual File System) makes your SAFE network storage appear on your device like a local hard drive. So any application you use can save or load files to and from your SAFE storage, including when you use the command line (which is what makes it such a good demo - see below). So it’s also able to function like a command line version of the Web Hosting Manager (WHM), and provides both a locally mounted drive with access to all your SAFE storage (_public, _private etc) and a way to create public IDs and SAFE services with simple commands. It was originally built in Ruby by @anon71598723 on alpha1 but has not been updated for alpha2.
I’ve pestered several joiners over time (sorry @JohnVonNeumann and @brianp to name two ) trying to find somebody who would like to update it but so far this awesome project has languished, so…
I’d like to suggest it as a low cost (code already exists) high value project for the CEP. Please click Vote above this post if you want this to happen.
Being able to register a domain and create a website and publish it forever with four commands is a demo that will blow anyone who can understand it away.
@happybeing I thought the virtual file system was so SAFE showed up on your computer as a virtual drive for storage. I guess I’m confused by the publishing a simple Safe site as this can be done with the web hosting manager. Just looking for some clarification. Thanks
And of course directory path ‘public/my-dir’ has to be in a correctly mounted directory, like described here:
Ps: Maybe it is also possible and useful to change the now on Github popular file uploader Uppy to also be able to upload/download files from the Safe Network? To be clear: I’m not saying this has to be a CEP idea, nor do I garantuee that I have time to do this myself.
This is also brilliant because if someone also runs a personal webserver on the regular internet, then /public could also be mapped to /var/www allowing for the website to simultaneously exist on both the regular internet and SafeNet at the exact same time.
Then when regular Internet users see all of the “safenet stuff” all over the website and they wonder “SafeNet? Whats that?” — now your website has also just doubled as a PR campaign for SafeNet, with no hard sell required!
It’s an interesting idea, but won’t work very well because only static websites (ie sites which don’t use the SAFE API at all) would function correctly, and is hard to see this as introducing people to SAFE unless that is the purpose of the site.
I’m curious about innovative ways to introduce people to SAFE such as this though.
I think it would world great for limited function, as you already stated. Often times, a static website is all someone needs. In those instances, this of course would work well.
One thing I am totally unsure of, is how it would translate the other way. What I mean is – what if a site is running e107 or Joomla or PhpNuke or something that the Apache Web Server is handling? If someone on the SafeNet side tried to use the site, would the Apache Web Server respond at all? If not, then things that require php, etc would not function on the SafeNet end of things. If however the SafeNet side were able to recognize regular http and https links (I think it can, yeah?) then it would activate those functions via the regular internet way.
As for SafeNet functions on the web, some sort of gateway bridge would need to be created and I’m sure even that would be limited, at least at first.
But even having a little bit of function and the site being able to co-exist on both networks, is still cool just in and of itself. Besides, even if a “limited function gateway” was created, limiting a function to prompt the user for the option of an upgrade, is a workable marketing strategy.
Just as you can tell code to only display a message if a person is using a particular browser, you can have messages inside of a website that only display if they are not viewing the site from the SafeNet side of things.
There might be a text box or line of text next to a function that says something like “SafeNet features are limited outside of SafeNet. Click Here for details on how to activate full functionality. Using SafeNet is completely free of charge”.
Another idea that just came to mind on this, is how to power a script that accesses SafeNet functionality from the “regular internet side” of things. You make a script similar to how WebTorrent operates.
With WebTorrent, this allows a regular website to not need much of its own bandwidth to deliver content. The users of the website are sharing their bandwidth as they use the site. The users are not required to download or install any software to be able to do this.
Similarly, a web script could be created for regular websites that allow regular Internet users to act as temporary SafeNet nodes. This would allow them to share their bandwidth with SafeNet as they browse a SafeNet powered site via the regular Internet.