diff --git a/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN.mdwn b/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN.mdwn index 6401148e0f..2974b157da 100644 --- a/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN.mdwn +++ b/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN.mdwn @@ -1,5 +1,26 @@ -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. +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. -Currently, `git-annex` depends on Tor and [Magic Wormhole](https://github.com/magic-wormhole/magic-wormhole) to share/collaborate/sync with others. There is [Hypercore](https://docs.pears.com/building-blocks/hypercore) by [Holepunch](https://holepunch.to/), but [Named Data Networking (NDN)](https://named-data.net/project/archoverview/) ([video](https://youtu.be/qbAB0iN1-zQ)) offers a more robust internet backbone. +Currently, `git-annex` depends on Tor and [Magic +Wormhole](https://github.com/magic-wormhole/magic-wormhole) to +share/collaborate/sync with others. There is +[Hypercore](https://docs.pears.com/building-blocks/hypercore) by +[Holepunch](https://holepunch.to/), but [Named Data Networking +(NDN)](https://named-data.net/project/archoverview/) +([video](https://youtu.be/qbAB0iN1-zQ)) offers a more robust internet +backbone. -Even better, there was an experiment for "[Distributed Git over Named Data Networking](https://github.com/JonnyKong/GitSync)" and [npChat](https://github.com/named-data-mobile/ndn-photo-app/issues/186) 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? +Even better, there was an experiment for "[Distributed Git over Named Data +Networking](https://github.com/JonnyKong/GitSync)" and +[npChat](https://github.com/named-data-mobile/ndn-photo-app/issues/186) +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? + +> treating this as a duplicate of [[todo/generic_p2p_socket_transport]]; +> [[done]] --[[Joey]] diff --git a/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN/comment_1_f511d430a948a9048eb8e8cede047bd4._comment b/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN/comment_1_f511d430a948a9048eb8e8cede047bd4._comment new file mode 100644 index 0000000000..8a053cada9 --- /dev/null +++ b/doc/todo/Abstract__44__LibreVault__44__ResilioSync_alternative_on_NDN/comment_1_f511d430a948a9048eb8e8cede047bd4._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2025-04-15T13:31:34Z" + content=""" +Honestly, your message somewhat triggered my internal spam filters. In +particular, its linking to multiple proprietary services adjacent to +glowing language about them. Also the very +similar language and linking in your post at +. + +For this reason, I have removed some hyperlinks from your post. +While I think, on review, that you are acting in good faith, +I also think it's important you understand a post like this can +cause that kind of reaction these days. And removing the links +will thus help no matter what. + +--- + +There is actually an open todo at [[todo/generic_p2p_socket_transport]] +which I think could probably be used to implement what you are envisioning. + +So my suggestion is you review that proposed design and see if it would +support the use cases you are envisioning. And if not, what changes would +need to be made. +"""]]