kxra@ae0f8ab3caa4ebebe6b1a121dd41b6751182360e 2025-04-15 21:23:33 +00:00 committed by admin
parent f48013fe43
commit 287172f9f5

View file

@ -1,10 +1,11 @@
Average users could get so much value out of a simple and intuitive p2p
file-syncing service that is as polished as ResilioSync
(https://www.resilio.com/sync/), provides revision control on arbitrary
files like Abstract (version control for designers)
(https://www.goabstract.com/), but open source like LibreVault, SyncThing
and SparkleShare. This would be priceless for science, design, all sorts of
collaborative workspaces, and especially for backups and data redundancy.
file-syncing service that is as polished as ResilioSync (formerly BitTorrent
Sync), provides revision control on arbitrary files like Abstract (version
control for designers) (https://www.goabstract.com/), but open source like
LibreVault & SyncThing, plus backed by a distributed revision/version control
system (DRCS/DVCS)¹ like SparkleShare. This would be priceless for science,
design, all sorts of collaborative workspaces, and especially for backups and
data redundancy.
Currently, `git-annex` depends on Tor and [Magic
Wormhole](https://github.com/magic-wormhole/magic-wormhole) to
@ -22,5 +23,12 @@ both exist. Could NDN be used as the backbone for a built-in method for
connections to be made for `git-annex` and set the foundation—pave the
way—for the perfect file synchronization/sharing app?
_¹ Although, it might be nice to use
[Pijul](https://pijul.org/manual/why_pijul.html), which has [efficient
binary diffs](https://pijul.org/posts/2021-06-28-two-changes/) and
hopefully someday also [word-by-word d
iffs](https://discourse.pijul.org/t/fast-characterwise-and-binary-patches/32/9)
(for example, to be the revision control system for a wiki)_
> treating this as a duplicate of [[todo/generic_p2p_socket_transport]];
> [[done]] --[[Joey]]