Hi Mat, I can't say it will be exactly like TiddlySpot. I don't know what all they do in the back-end. I would hope it turns out as reliable as TiddlySpot, but I'm not sure I can live up to their proven track record.
Plus, wikis will be at https://wiki.<domain>/wikiname What I am planning is that it will be public, it will be free up to the capacity of the VPS I'm running it on. I can only hope it will be sufficiently reliable since I plan on using it myself. I'm making it because of 2 concerns I have with the lack of ssl on TiddlySpot. First, the tiddlywiki credentials are passed over the Internet encrypted, which is not a good idea. Using HTTPS solves that. Secondly, the various store.php scripts I've found use plain text password storage. I don't know if that includes the variant that TiddlySpot uses. I plan to fix that on my version this weekend and store the passwords using the same encryption supported by the lighttpd server for basic authentication. I have already paid for a tiny VPS from Liteserver.nl for a year (the really small 256 MB of RAM one). It's setup with Debian Linux, Lighttpd, and php5. The SSL certificate is provided by Let's Encrypt. The current domain is my personal domain. I plan on moving one of the wikis I have a TiddlySpot over to my own system once I'm happy with the setup and stability. I have 2 wikis on tiddlyspot, the other one will stay there. In terms of features that I feel are needed (on my system) for it to be considered ready for public access: * https only for accessing the wikis (done) * wiki user's passwords will be stored in a secure manner (crypt encrypted or apache digest auth (salted MD5). * each wiki in it's own directory, including a backup directory (backups beyond a certain age will be purged) (done) * a sign-up page (done) * a user control area where the wiki owner can change his/her password or cancel his/her account * limit on size of wiki (this is a php upload setting, currently 8MB but I may change it depending on performance, probably not smaller). Right now I lack the encrypted password storage and the user control panel. After that I hope to add: * A selection of template wikis to choose from during account creation (like TiddlySpot). * Support for multiple wiki users of a single wiki (managed by the wiki owner). * Option for a wiki owner to request a zip file of their wiki and all saved backups. * Option for wiki owners to generate a static version of their wiki (similar to tiddlywiki/static) if I can ever figure out how to get node.js to do that. * A pretty list of hosted wikis, being added to the list is at wiki owner's choice, it will be opt-in if it ever happens. On Thursday, March 16, 2017 at 3:56:13 PM UTC-4, Mat wrote: > > Hello Lost Admin! > > I'm not sure I understand - is your intention to create a service like > more or less exactly like TiddlySpot, but with https? > > ...and to run it like cousins Simon and Daniel Bard do with TiddlySpot is > run, i.e public, free, reliable etc???? > > That would be incredibly generous. But I must assume I misunderstand > something because that would be quite a moral commitment considering how > people truly rely on TiddlySpot. Of course, your project is interesting > even if do, in deed, misunderstand your intention! ;-) ;-) > > So, if I may, exactly what *is* you intention? > > Thanks! > > <:-) > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/005ce31e-7080-4106-aec0-8af6f501dd58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
