Hello. I remember a long time ago I found some protocol that was boasted as a less out-dated version of bittorrent. I think one of its features was that you could update a whatever-their-equivalent-of-a-torrent-is with small changes and those changes could be seeded.

If this sounds familiar, and you know anything about this, I would really appreciate pointing me in the right direction. Thank you.

  • 3h5Hne7t1K@lemmy.world
    82·
    1 year ago

    I would also add IPFS, a REALLY cool piece of tech.

    Some really interesting suggestions in this thread that i will definately look into when i find the time.

    • Sl00k@programming.dev
      7·
      1 year ago

      I think the problem with IPFS is it’s terribly inefficient with large and or dynamic data storages, the exact problem bittorent tackles(large not dynamic).

      IPFS does seem to provide great p2p functionality for small static files though, albeit pretty slow.

      • agilob@programming.devEnglish
        1·
        1 year ago

        also data duplication, if you want to store a file in application readable format and IPFS you need to store TWO files, makes archiving and management expensive

      • Nato Boram@lemm.eeEnglish
        1·
        1 year ago

        Yeah, the discovery process is shite on IPFS. You kinda have to cheat it to get it to work with something like .

        Idk if it’s inefficient with large data, but it’s inefficient with compressed storage, as it does block-level deduplication, which is very cool.

  • eu8@lemmy.worldOP
    4·
    1 year ago

    To potentially answer my own question: I believe the protocol I was looking for might have been the dat protocol which seems to have been replaced by something else.