Hi all,
- I’m a ‘backend’ guy, pretty much all my ‘TW’ frontend stuff is based on startup macros that use message ‘Hooks’- either standard ones or ones I covertly ‘sneak’ into $tw in my TiddlyWikis. These send requests to a server. Granted - the server doesn’t process data - use the client side processor, memory, bandwidth and resources to do the grunt work - server just takes in, ‘wash, rinse, dry, repeat’, and out. So the server can handle a vast number of users.
Main Topic!
I notice that ‘TW-MMO’ ‘TiddlyWiki Massively Multiplayer Online’ seems to be of some interest? Is where future of TW should be? Or if not - what do you see is TW future path?
Please reply - give this thread some traction.
Ugly attempt years ago - but did work!
-
My son and I - way before nodejs TW! built a server backend system with ExpressJs v0.0.0.0.1 (joking!) that stored each user TWiki on their own git branch ‘username-tw’ that only that user c/would access. For each user, “tiddlywiki-tiddler-store” (ie: standard tiddlers) where stripped out before commit to ‘username-tw’!
-
Those standard tiddlers were stored on the users ‘other’ branch ‘username-tids’ - which is merged/fetched/pulled/rebased (whatever - in sync!!) - with ‘main-tids’ - master back then. So ‘main-tids’ has all tiddlers from all users on the server - so your ‘username-tids’ branch is up to date.
-
So, when you request ‘MyTWStuff.html’ (or any TWiki you uploaded to server) - the server injects your ‘username-tids’ branch tiddlers into ‘that’ MyTWStuff.html and delivers, with has EVERYbody’s standard tiddlers.
This is a a birds eye view of the birds view of the birds. Ryan - my son - thinks he has the old Express stuff - But so old - probably but should whip this up from scratch. I got all the server side stuff - tw - frondend tiddler stufff - not so much!
Any interest in a TW-MMO?
Please advise
poc2go


)