Article type: Fundamental
Article name: Experimental - Flexible Sync Model
Author: Framez


Description:

online-offline flexible sync, high availability model

Many web apps today are built with the basic premise that you will simply have internet. And if you don’t, you can’t use the app.

Listiary is built with decentralization, high availability, and irregular data syncing upstream or downstream in mind.

The reason is twofold. For one, we want to give the user the basic right to control where the data comes from vs. where the app talks to.

For another, as a wiki knowledge system, we want a decentralized system with baked-in resilience that serves the user best and can survive splinter-net, a nuclear holocaust, and a cyborg uprising, not a service that disappears the first time there is a Google or AWS outage, or changes its terms when the people running it change their mind.

Basically, I believe a user should be in control of what gets pulled locally, what gets synced, where it gets synced to, and when, if they want to. And they shouldn’t be bothered by it if they don’t.



Back