Need an official sync service

[linonetwo]

I feel handling sync between mobile and desktop taking too much of my time. I'm putting these time to AI & biology, but still sometimes tidgi mobile & desktop users reporting bugs. I hope tw core team could provide an official solution, so I don't need to. Just like I choose tw as a platfrom to develop my app so I don't need to handle plugin mechanism and widget system.

Would you offer a paid sync service like Obsidian team? It could based on tiddlyweb API, and should work aloneside other sync-adaptors (filesystem-adaptor & sqlite-syncadaptor) so it also works locally.
And it should handle the conflict.

I think this could also make a decent amount of money for the team. Like Obsidian team is feed by its sync service only.
P.S. If you want to earn more money, you could provide an official AI service like openrouter, Notion earn money from notion AI much more than its sync service subscription.

[Leilei332]

Noteself supports saving through punchdb. Sadly, it hasn't updated since 4 years ago.

[joshuafontany]

I think we are getting close to that with the ES2017 refsctor & the MultiWikiServet work.

"Official" comes with a lot of memetic baggage: supporting accounts/identity/logins(password resets, ugh), encrypting user data so it does not bleed and "leak" between users or groups, managing any sort of social network profiles/graphs, some sort of support channel, etc.

The Kinopio.club team (very small AWS hosted encrypted Whiteboard/concept mapping) has done it.

I think it is very doable, and with smart api key management, you could have a small version of the server running "locally" and support syncing to the cloud & your local machine.

We have a rough start on other aspects, like the official TW forum & discord.

I expect to have a lot more free time & expendable mana points soon (just finished buying a house, so stress level peaked this week). Let's keep this design discussion going.

I have my ideas, but want to see what the community thinks before rushing to technical details. 😉

[pmario]

I think MWS Muliti Wiki Server will be an option, once it is finished. I'd consider it alpha at the moment. @Arlen22 ... What do you say?

[Arlen22]

I can pretty easily add more sync stuff to MWS, but knowing what sync stuff I need to add is the main problem, so I'm more interested in seeing what existing solutions are available and adapting them to MWS.

So far I've been working on batch syncing (all tiddlers at once) and using server-sent events to trigger an immediate sync, but those are very much still using the existing syncer paradigms. There are other paradigms, like synced local-first sqlite DBs that could also be viable solutions.

The key point is that all of these syncing solutions usually benefit more than just MWS, as MWS is just one of a number of existing server solutions with various use cases, and most of the work involves adapting the TiddlyWiki client to using that particular syncer. The server part is usually quite trivial, in my opinion.