I am a web designer (not developer). I have put a lot of time and money into my membership sites (UFO experiencer sites)… What happens to existing sites when this becomes the new internet?
Will I have to become a developer to create sites? Will my old sites be obsolete?
Response (Editable by anyone)
For static content/html all you need to do is copy all the files to a public share on SAFE and they can be accessed directly by a standard web browser. A SAFE aware web browser will be able to resolve a SAFE URL (something like “safe:DanaD/public/mysite/”), while a browser that doesn’t know how to do this would need to access the files using the locally mounted SAFE drive, which worksas if the files were stored on a local drive.
However, very little of today’s web is static, which is a problem!
Most websites use a backend database (CMS) and generate the HTML dynamically from this for every page request submitted by the browser.
So in most cases there will be a need to either:
A) Convert them to static HTML and lose the functionality of CMS and many end user features
B) enable these legacy systems to run on the client, using SAFE just for the data.
C) port them to a new SAFE based CMS style architecture
Only C) is at all satisfactory IMO, because:
A) will simply not work for most websites, and where it does will have reduced end user features and be expensive to maintain. I think an app to do this conversation will be useful and very popular (Convert Your Website To SAFE!), but will also show these limitations very quickly.
B) is a cludge, but technically straightforward and will preserve most of the user experience and CMS features of the website, keeping the websites both functional and easy to maintain. It will however require every user to have a full database backend and web server installed, which therefore requires an installer to be developed and adopted by the website builders, and for users to have set it up before they can use these websites.
C) Is the long term solution and needs to be developed pretty much from scratch, probably in stages: stage one being a browser extension to access static HTML websites hosted on SAFE. This gradually being enhanced to replace the backend and server features of B), first within the plugin, and later within a native SAFE browser.
The first plugin is under development - route C). I’m not aware of people working in A) or B).
The opportunity is huge though, for obvious reasons, so I expect that a successful SAFE launch will be followed by a lot of interest and activity in this area. So don’t despair!