There are now many technologies for P2P file sharing:

  • Usenet
  • Bittorrent
  • IPFS
  • Tenfinger
  • more?

And also several technologies for anonymization:

  • VPNs
  • Tor
  • I2P

AFAICT the most popular option is still Bittorrent with various public and private trackers and indexers. Private trackers seem to be the most effective option that communities have converged on.

I’ve tried all of the above solutions over the years and while I think something like I2P sounds great in theory, it doesn’t seem to actually work well in practice. Because it’s not terribly popular, it’s hard to know what to expect.

We clearly still haven’t found the ideal model that can provide both good performance, discovery, access, availability, and anonymity. But do you think we will actually make progress on these problems? We seem to have stabilized on a local maximum.

    • pedroapero@lemmy.mlEnglish
      1·
      1 day ago

      I stumbled upon it this weekend, it’s impressive! Looks like the original IPFS vision: uniquely identifiable files. Much more simple: no custom DHT, no block identifier, just blake3 CIDs and Mainline DHT. So less potential scalability issues, less protocol complexity, less swarm fragmentation. And written is rust. https://github.com/n0-computer/iroh-share/

  • dan@upvote.auEnglish
    0·
    18 days ago

    Usenet is client-server, not P2P.

    The issue with “good performance” on P2P systems is that you’re reliant on other users’ bandwidth, and there’s a lot of people in the world that have slow upload speeds. Some users use a seedbox with a fast datacenter-grade 10Gbps or 40Gbps connection, but it’s not common.

    The obvious approach if you want to download something from people with slow connections is to download parts of the same files from a lot of them in parallel, which is exactly what BitTorrent does. That’s good enough for plenty of use cases, which is why BitTorrent has been around for so long. The protocol is designed pretty well for this use case.

    It’s got plenty of legit use cases too, especially in research (where it’s common to have data files that are tens or hundreds of gigabytes and need to be shared with other researchers) and in gaming (where it was common to use BitTorrent to download updates, at least outside of Steam).

      • dan@upvote.auEnglish
        0·
        17 days ago

        That’s not what P2P means though. With Usenet, the articles are stored on a server, and you download them from the server. P2P always means one peer directly connects to another. The reason P2P systems exist is that they avoid things like takedowns (since you’d need to take down every user instead of a central server), and Usenet doesn’t have that advantage.

        If Usenet is P2P, then every other system that lets people upload files is P2P, including things like Rapidshare, Google Drive, forums, etc. That wouldn’t make sense.

        • MEtrINeS@lemmy.dbzer0.comEnglish
          0·
          17 days ago

          then every other system that lets people upload files is P2P, including things like Rapidshare, Google Drive, forums, etc. That wouldn’t make sense.

          P2P means peer to peer.

          Here you have a graphical description of usenet: https://en.wikipedia.org/wiki/Usenet#/media/File:Usenet_servers_and_clients.svg

          From wikipedia https://en.wikipedia.org/wiki/Usenet

          When a user posts an article, it is initially only available on that user’s news server. Each news server talks to one or more other servers (its “newsfeeds”) and exchanges articles with them. In this fashion, the article is copied from server to server and should eventually reach every server in the network

          Please pay attention to: Each news server talks to one or more other servers (its “newsfeeds”) and exchanges articles with them.

          hmmm… it sounds like p2p.

          Here you have the fucking RFC for the command to share articles between servers: https://www.rfc-editor.org/info/rfc3977/#section-6.3.2

          Even if you check the article headers you can see the path the article it took to reach to you. If the article wasn’t uploaded to your server, you can see that some articles that you are downloading came from different servers until it reached your server.

          Tell me, if rapidshare, mega, google drive, etc works like this. Well i don’t think so, because first you don’t even have different servers from different providers… You just have their servers, so they can’t share shit with anybody else’s servers.

          It’s not p2p for the enduser, but that’s why i said it was server p2p.

          OR maybe you operated a NNTP server with only 1 feed? (which i doubt).

          The reason P2P systems exist is that they avoid things like takedowns (since you’d need to take down every user instead of a central server), and Usenet doesn’t have that advantage.

          If you had used usenet before obfuscation took place, you could see that some articles where removed from some server but still available on another ones. That’s why there was a rule of having servers from different backbones https://cdn.rexum.space/usenet/Usenet Providers and Backbones (Version 2025-06-30).svg

          • dan@upvote.auEnglish
            1·
            17 days ago

            Please pay attention to: Each news server talks to one or more other servers (its “newsfeeds”) and exchanges articles with them.

            hmmm… it sounds like p2p.

            This is describing federation and decentralization, not P2P. The servers communicate with each other. P2P is when users communicate directly.

            Would you consider Lemmy or email as P2P? They’re also federated and decentralized.

            It’s not p2p for the enduser, but that’s why i said it was server p2p.

            Your definition of “server P2P” doesn’t really make sense. Any CDN would fit this definition for example, because CDN edge servers fill data from origin servers when it’s not cached locally, and a lot of that data would be user-uploaded, but I’m not sure anyone would describe Akamai, Fastly, or Cloudflare as P2P.

            Usenet has companies running the servers, and you download from and upload to the company’s servers. Nobody would reasonably describe that as P2P, regardless of how the servers are implemented.

  • BlueÆther@no.lastname.nzEnglish
    0·
    19 days ago

    Ive trued private trackers, but there is very little for me to try and keep up the ratio them while on public my share ratio is well above 5.

    Public trackers and no vpn gets it done

      • BlueÆther@no.lastname.nzEnglish
        0·
        19 days ago

        see, I don’t really do popular (except for the kids) and private trackers just seemed like too much hard work

        • W98BSoD@lemmy.dbzer0.comEnglish
          0·
          19 days ago

          Keep seeding and your ratio goes up, even if people aren’t downloading the file.

          Or, donate to the site.

          Most people do the former and that’s perfectly fine.

          • Damage@feddit.itEnglish
            01·
            18 days ago

            Donating means either having a trace that links you to an illegal entity, or getting into the crypto mess

            • 14th_cylon@lemmy.zipEnglish
              01·
              18 days ago

              getting into the crypto mess

              which leaves the trace as well, don’t kid yourself that crypto is anonymous