First of all, no one get too excited, I’m just testing the waters while I get reacquainted with the safe network APIs.
SAFE Network publishing tools
I’ve spent the last couple of days reading through a lot of the app related posts in this (and other) forums, trying to grok how I fit in to this bold new world of SAFE.
One of the most perpetually popular ideas for an app seems to be publishing tools, a la Wordpress. You can see the hype around tools like Safe-CMS and Safepress and the appetite doesn’t seem to have died down at all - in fact, there seems an almost melancholy at the lack of quality publishing tools.
I’m still interested in creating website publishing tools, and wanted to guage public interest before I made any sort of decision.
Where we went wrong last time
In my opinion, the original Safe-CMS was a flawed project:
- It was an electron app, this meant that updates had to update local executable programs, which is always messy. Electron apps take up a lot of RAM, a lot of system space, and ultimately it’s just a lazy wrapper for a website. It’s much easier and quicker to simply go to a web address within the SAFE browser.
- By virtue of it being an app, people had to download it from the clearnet, meaning that without some sort of complex (and expensive) application signing certificate there was no way to prove that builds hadn’t been tampered with.(it just wasn’t financially feasible to be delivering 300MB of data over SAFE network for every download).
- The code for the app wasn’t public at the time and ended up being lost to the ether due to me being a key-man-dependency.
If I created any follow up project to Safe-CMS, it would have to abide by the following doctrine:
- It would have to live within the SAFE network, as a web application.
- It should have zero clearnet dependencies.
- It would have to be open source from the very beginning, with the source available via Github.
Like I said, I’m just gauging public opinion. If there’s significant interest I’ll strongly consider setting forth plans and putting out a development timeline. If not, I’ll keep thinking.