To be clear, the $100/month is a quick estimate of the server costs for a 
shared community server, a personal one would easily fit on a cheap digital 
ocean droplet for US$5/month.

I have had a raspberry pi 2 as my local server running Bob and a few other 
things (gitlab, droppy and some custom server things I made) for a few 
years without any trouble.

On Tuesday, December 22, 2020 at 11:05:17 AM UTC+1 Jed Carty wrote:

> Hello all,
>
> The short version: I have a potential replacement for tiddlyspot that 
> could be distributed and self-hosted on something small like a digital 
> ocean droplet. My computer died and help getting a new one would greatly 
> speed up the development and release.
> I think that a community managed public server is a good idea, and it is 
> designed so that you can create your own private server.
>
> The long version:
> I made a server that works with Bob and TiddlyWiki that adds a secure 
> token-based login that is appropriate for having a web-facing server. I 
> have been working on this periodically for a while, some of you may have 
> seen it when I had Ooktech.xyz up. I have been working on it periodically 
> for a long time and it is very close to ready for public release.
>
> The problem is that an adorable kitten decided that dancing on my 
> multiprise was a good idea and after some impressive sparks the computer I 
> do my development on is dead. The kitten is fine and acts adorably innocent.
>
> The server has all the features of Bob (multiple wikis, everything 
> configured from within the wiki itself, support for multiple simultaneous 
> users), as well as a secure login using JWT (json web tokens). Accounts 
> have granular permissions which can be set, there many but here is a quick 
> incomplete description of what you can do, in no real order. Server 
> administrators can enable or disable almost all of these features if they 
> are not useful for your purposes.
>
> - A simple script to run that sets everything up
> - Publicly viewable or private wikis
>   - Allow specific people to view or edit a wiki
> - If an account owns a wiki they can set permissions on their own wikis
> - optional quotas for accounts both in terms of number of wikis and storage
> - A plugin library built into the server
> - Access controls for plugins as well (so plugins can be used to 
> distribute content 
>   without making it public)
> - Simple 1-click download for wikis as a single-file without Bob
> - profiles/accounts and wikis can be set as private so on one can see them
> - Create an account on the server from a wiki
>   - update passwords and other account information from inside a wiki
>   - accounts can have some 'about me' information, if they want to set it
> - Set if an account can create wikis
> - namespaces wikis (if I create a wiki called MyWiki it would be 
> inmysocks/MyWiki) so 
>   that there are no naming conflicts
> - change ownership of a wiki (give a wiki to someone else)
> - inter-wiki federation, like chat and sharing tiddlers between wikis
>
> There are many other details about administrator controls, but those are I 
> think the highlights for using the server. Almost all of that is 
> implemented, I am in the process of adding usable in-wiki interfaces for 
> all of it.
> The setup script is only currently for linux and osx, I would need someone 
> who is familiar with windows to make that if anyone wants it. Hosting 
> online is generally linux so I am not sure how much it would be needed.
>
> My plan is to put up a demo site as soon as I can that has limited 
> life-time accounts to show the features. You could create an account that 
> lasts a day and after the account and wikis with it are removed.
>
> I am not interested in hosting and running this myself, it would be a 
> community with community governance supported by donations. I do not know 
> the demands that would be put on it, but I don't think that the hosting 
> costs would be more than about $100/month.
> I would of course continue updating the server, but maintenance and 
> operation must be a group effort so we don't get a situation like 
> tiddlyspot where we rely on two people who may not be active members of the 
> community and we have no way to shift ownership for continued operation.
>
> I don't know what interest there is in this, so I am going to gauge that 
> from the response to this post. Also, help with getting a development 
> computer would speed things up a lot.
>
> A link to the amazon wishilst for the computer components: 
> https://www.amazon.fr/hz/wishlist/ls/2WM0S9VV3LJR1?ref_=wl_share
>
> ps:
>
> There are a lot of future features that I am working on, like the ability 
> to search multiple wikis from one wiki, inter-server federation so you can 
> have your own private server and interact with other servers, having a 
> login on one server that lets you access wikis on other servers, things 
> like that.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/aae34e8b-c074-494a-ba04-d2e668e3823dn%40googlegroups.com.

Reply via email to