no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
17 comments in c/piracy@lemmy.dbzer0.com view that post
[–] 7 points 2 weeks ago (2 children)

I can’t help but think about this while reading this post. However, this is probably indicative of my lack of understanding of computer networks, despite dealing with it from time to time.

  • source
  • hideshow 2 child comments
  • [–] [S] 11 points 2 weeks ago* (1 child)

    Sorry for that! Basic is: it's fully decentralized, and when anyone starts sharing a file, it joins a unique swarm of seeders. Whereas on Bittorrent, there is one swarm for each torrent, each private tracker for the same file, and also for folders (TV episode; TV season; TV series); this is called "swarm fragmentation" and leads to low speed and dead torrents.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 2 weeks ago* (7 children)

    What is your view on veilid as compared to this?

  • source
  • hideshow 7 child comments
  • [–] [S] 3 points 2 weeks ago* (last edited 2 weeks ago) (6 children)

    First time I hear of it. They say this is for private networking only. Also it's only a network stack for now (the "BlockStore" storage component is not yet defined). So apparently it's not for public filesharing. They compare it to Tor but it looks more like an overlay mesh network at first sight.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 2 weeks ago (5 children)

    I really like two of their points:

    • anonymous by design
    • distributed as a library

    I really hate because such projects as IPFS required me to install some extention and a niche component that is hard to understand. While it is easy for me to do it I have abandoned all hope that project like this would gain some broader popularity.

    For example qbittorrent is already hard to use for most people and it does not require to install extention and background service. You just install an app.

  • source
  • parent
  • hideshow 5 child comments
  • [–] [S] 3 points 2 weeks ago* (last edited 2 weeks ago) (1 child)

    For Iroh-blobs, Dropwire would be the easy-to use all-in-one app (not appropriate for mass sharing just yet). Then there is the iroh-http library, allowing to use Iroh-blobs on a web browser (without installing anything; a website similar to instant.io / webtorrent.io).
    Also note that most of the big Bittorrent peers have a pretty sophisticated setup anyway (allways-on machine with raid array; bittorrent daemons; remote client; VPN; download automation indexers; media library etc).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 weeks ago (2 children)

    FWIW, you can access IPFS content with an in-browser IPFS gateway now, so no need to install anything: https://inbrowser.link/

    You'll still need to install something if you want to add/pin content, etc., but the in-browser gateway is convenient for sharing links to IPFS stuff with someone who doesn't know what IPFS is.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 weeks ago (1 child)

    Any mutability or just immutable?

  • source
  • hideshow 1 child comment
  • [–] 1 point 1 week ago* (last edited 1 week ago) (3 children)

    iroh-share is not decentralized filesharing.
    iroh seems like a stack. like https://libp2p.io/docs/
    eventually they may have a tool that does decentralized filesharing.
    and if i was going to dev my own solution from scratch, iroh would be my pick.
    but i'm lazy so i use ipfs(kubo) . it works
    update: i now see that iroh has https://github.com/n0-computer/iroh-share
    however it does not share partial pieces like bittorent and ipfs .
    in many cases, that might actually be more efficient (like an ordinary download).
    and from my understanding: it supports multiple providers as the source. ( so it is decentralized ).
    i think there are advantages and drawbacks.

  • source
  • hideshow 3 child comments
  • [–] [S] 1 point 1 week ago* (2 children)

    From my understanding, peers stream merkle-tree leaves to the requester, allowing to verify data while downloading: https://docs.rs/iroh-blobs/latest/iroh_blobs/protocol/index.html#responses
    So it does have piece chunking for large files, which correspond to the native Blake3 chunks.
    The same goes for shared directories (sharing each file root blake3), I think this is called a "Collection".

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 6 days ago* (1 child)

    i think https://github.com/mrsarthi/Chorrent is a better bittorrent/ipfs replacement.
    from my understanding, iroh-share is like ipfs-style global uploads, and then can be fetched from any peer with continuation ( like wget -c ) .

  • source
  • parent
  • hideshow 1 child comment