Hi all. Still catching up on the recent development work, threads, and the multi-wiki-server branch.
I have a stable deployment setup that allows me to run multiple MWS servers on a single machine. (See the TW w/ NGINX threads.) With a custom hosts file (that maps domains to my local ip addresses) I can type in `{topic}.gyld.local’ and get a MWS for that topic (some setup required, lol).
I am getting ready to expose this to the internet (at first for my family’s use) w/ https/security enabled.
Next steps:
-
Integrate logins via BlueSky’s ATProtocol
- “DID” (distributed identity documents) allows cryotographically signing wiki updates.
- Manage MWS user list with “well trusted” identities.
- Allows integration with BlueSky feeds and other ATProtocol apps.
-
Realtime sync with Yjs
- Extend the new MWS sqlite “store” with Yjs CRDT (conflict free replicated datatypes) to allow real-time conflict free syncing.
-
Integration with a new social platform called “Kowloon” that uses very interesting user-controlled social-graph concepts (in early alpha).
-
Integration with other services like Google Drive, etc.
-
TiddlyWiki-on-BlueSky-as-a-Service
- This is the least refined point, but once I have the ATProtocol logins & Yjs sync all working, the idea would be to offer a “cloud” based service that would spin up one MWS virtual machine per user and bind it to their BlueSky identity. Then, allow that user to admin/invite other users to certain wiki’s on their virtual machine.
- Wikis would like at an address like: joshuafontany.bsky.social.gyld.app/wikis/MyRPGWiki
Or
tiddlywiki.org.gyld.app/wikis/TiddlywikiDev
(You can set your BlueSky username to any domain you control by hosting a DID there yourself.)
This naming schema is totally back-of-the-napkin, & resources (actual vm costs) would be managed via an OpenCollective. Free accounts would probably have to have limited storage & we would need to figure out media hosting for uploaded files & database backups.
I hope this sparked some fun ideas. Watch this space. 