Bringing it all together

There’s basically enough pieces of innovation available here now individually for me to replace something like Monday-dot-com which is the collaborative task management, collaborative document platform I’ve chosen for my department. It’s a frustrating to use platform and expensive, but does the minimum things I need it to do.

Somehow, I’d have to combine

  1. TiddlyWiki core and plugin architecture
  2. Per-tiddler online/offline realtime sync like PWA (valpacket/btheado)
  3. Reliable hosting for syncing service (like TH/simon)
  4. Multi-user permissions system like from MWS (Arlen22)
  5. Desktop app and iPhone/Android apps like from TDRS (BurningTreeC)

I’ve found value with each of them independently, but always get stuck bringing them together

  • #3 isn’t useful to me without features of #2 (offline editing)
  • #4 can’t help me without features of #5 (install without admin)

I’m curious if anyone with more skill has had luck bringing it all together?

5 Likes

But the ads make Monday dot com sound amazing… Oh… Right…
I’ll give it a wide berth then.

Installing without admin rights sounds tricky, but…

#3 isn’t useful to me without features of #2 (offline editing)

What if you converted the wiki to be a Node wiki and ran it through something like TiddlyDesktop-RS, which comes with a node server built-in – or otherwise sandboxes the node server and runs it locally?

You can then layer a syncing solution on just the filesystem, targetting your tiddlywiki folder. In theory, you can do that on a regular consumer cloud syncing solution like OneDrive.

Your users just need to know they cannot touch the files directly in the filesystem while TiddlyDesktop-RS (i.e. the Node server) is running.

this is an interesting idea conceptually, surely such a product can be built and refined

one thing also that certainly come up - is there an API component also?

I think in the current TiddlyWiki environment the closest to your Nirvana would be a version of MWS (multiwik Server) hosted on your LAN or on the internet. Access can be through browsers or an app that is mostly just a browser. #2 and #3 syncing would be unnecessary on this model as it is built into the architecture.

There may still be gaps but it should be our job as a community to solve them. It would allow us to better compete with cloud and multi-user solution and even go beyond those. Not withstanding any gaps we find I believe the following strongly;

We have a lot of opportunities to build on top of the “TiddlyWiki Platform” a range of sophisticated solutions in the software layer, TiddlyWiki Script can be used to manage users, tiddlers they create and own, unique titles, tracking edits etc…

  • I have explored the techniques required for the vast majority of these mechanisms
  • I find it hard to rally the community around fixing any gaps I come across because its always from down in the weeds, and people are less likely to grasp the vision - of providing good solutions for multiuse team solutions.
- MWS (multiweek Server)
+ MWS (MultiWiki Server)

:wink:

I agree Tony that there’s lots of “close” configurations, and that’s the point. Frankly BOB.exe is still really the closest, though TDRS is catching up - especially if the real-time sync works as well as BOB’s websocket approach. LAN is however not an option in my corporate environment, but the PWA mechanism works. I have a box of all the right parts, but not the skill to assemble it.

Aside from the selfish personal need I have, I also bring this up because this seems like a reasonable path to having TiddlyWiki financially sustain itself. There are many tools I use in my work that has completely free and open source base, and then there’s a team-collaboration or hosting angle that a fraction of the user base needs, but that pays for the whole thing. When I go to TiddlyWiki and see a giant bulletin of “Hire Me” it just seems so obvious to me what the solution could be.

Until then, I’m stuck using TiddlyWiki only in my personal life, and using and paying for tools like Monday dot com that get the job done, but there’s a lot less joy in that.