3 ms·
A universal sync engine could be "files as zipped repositories." A repository as a file is self-contained, tracks changes by itself, and is, therefore, free fr
by samuelstros 2y ago
A universal sync engine could be "files as zipped repositories."
A repository as a file is self-contained, tracks changes by itself, and is, therefore, free from vendor lock-in. Here is my draft RFC https://docs.google.com/document/d/1sma0kYRlmr4TavZGa4EFiNZA_u4lLy0sOBMWHd0ctyY https://docs.google.com/document/d/1sma0kYRlmr4TavZGa4EFiNZA...
- threecheese 2y agoCan one apply a conflict resolving replication over the network using a zip archive? Genuinely asking; having a master-less distributed “database” that can be … distributed like a file sounds like it would solve a lot of portability problems.
- samuelstros 2y agoif conflict resolution has to happen in the network layer -> tbd. it seems like apps that have built-in conflict resolution can resolve conflicts. zip archives will play a role. i am pushing for "zipped repositories" internally, precisely for portability. but also because it makes the UX of using apps with conflict resolution like any other file-based software: simple. btw my rfc led to another one https://github.com/orgs/opral/discussions/2975 https://github.com/orgs/opral/discussions/2975. if we agree on the proposal, i will follow up soon with a "okay, we have repos now. let's zip them for portability"
- efreak 2y agoYou mean `git bundle`?