1. It doesn’t make you anonymous. Torrent protocol wasn’t designed with anonymity in mind and there are a million ways you’re going to leak your actual IP address.
  2. Tor is a TCP only network.
  3. While this doesn’t give you the anonymity you wanted, it will hurt the network for other users.
      • I2P is a P2P darknet. on tor the network is run by volenteers (~6000 nodes) while on I2P everyone on the nerwork is a node, and their are no built in exit nodes (in i2p their called outproxies). the official I2P router has a built in torrent client as well. like torrents the more people on i2p the faster the network, while the opposite is true for tor.

      • It is a different anonymity network, which works differently in many aspects.

        I2P and Tor comparison: https://geti2p.net/en/comparison/tor
        I2P on Bittorrent (mostly a client dev guide, but has some interesting info): https://geti2p.net/en/docs/applications/bittorrent

        Currently BiglyBt supports I2P and it has been that way for quite some time.
        If you use qBittorrent, I2P support will come in version 4.6. you can try it out now with the published release candidate version. Probably other clients are working on it too as the support is coming from the libtorrent programming library, which is used by other clients too.

        Right now, I2P is quite slow in my experience, in terms of loading I2P websites. I hope that it’s just a misconfiguration on my part, or that these specific sites I tried are just overloaded.

        • Near as I can tell:

          Tor is about privacy (and is prone to being compromised but…). So long as the exit nodes are in “friendly” countries and are run by trustworthy individuals (…), you are “safe”. And that is why it is popular among journalists. The downside being that a lot of heinous shit is done on Tor and those exit nodes are potentially liable for them.

          I2P is about avoiding censorship. Everyone is an exit node and cops kicking down doors doesn’t significantly hurt the network.

          But… I would very much NOT use that for torrenting. Because the endpoints can still be detected and recorded. And “I wasn’t downloading that Tay Swizzle concert, I was just letting potentially thousands of other people use my computer to download it… Why did you suddenly start laughing and talking about The Pirate Bay?”.

          And that also ignores the “darker” parts of the dark web. Where, rather than getting a letter from the MPAA you get a visit from Chris Hansen.

          • It is not true that every node is an exit node in I2P. The I2P protocol does not officially have exit nodes—all I2P communication terminates at some node within the I2P network, encrypted end-to-end. It is possible to run a local proxy server and make it accessible to other users as an I2P service, creating an “exit node” of sorts, but this is something that must be set up deliberately; it’s not the default or recommended configuration. Users would need to select a specific I2P proxy service (exit node) to forward non-I2P traffic through and configure their browser (or other network-based programs) to use it.

              •  nybble41   ( @nybble41@programming.dev ) 
                link
                fedilink
                English
                1
                edit-2
                11 months ago

                No, that’s not how I2P works.

                First, let’s start with the basics. An exit node is a node which interfaces between the encrypted network (I2P or Tor) and the regular Internet. A user attempting to access a regular Internet site over I2P or Tor would route their traffic through the encrypted network to an exit node, which then sends the request over the Internet without the I2P/Tor encryption. Responses follow the reverse path back to the user. Nodes which only establish encrypted connections to other I2P or Tor nodes, including ones used for internal (onion) routing, are not exit nodes.

                Both I2P and Tor support the creation of services hosted directly through the encrypted network. In Tor these are referred to as onion services and are accessed through *.onion hostnames. In I2P these internal services (*.i2p or *.b32) are the only kind of service the protocol directly supports—though you can configure a specific I2P service linked to a HTTP/HTTPS proxy to handle non-I2P URLs in the client configuration. There are only a few such proxy services as this is not how I2P is primarily intended to be used.

                Tor, by contrast, has built-in support for exit nodes. Routing traffic anonymously from Tor users to the Internet is the original model for the Tor network; onion services were added later. There is no need to choose an exit node in Tor—the system maintains a list and picks one automatically. Becoming a Tor exit node is a simple matter of enabling an option in the settings, whereas in I2P you would need to manually configure a proxy server, inform others about it, and have them adjust their proxy configuration to use it.

                If you set up an I2P node and do not go out of your way to expose a HTTP/HTTPS proxy as an I2P service then no traffic from the I2P network can be routed to non-I2P destinations via your node. This is equivalent to running a Tor internal, non-exit node, possibly hosting one or more onion services.

    • I keeps getting brought up because TOR is the most popular anonymizing network. It’s not far-fetched to think “how can I make myself anonymous while torrenting?” search for “how to be anonymous online”, find TOR and put two and two together. It happens all the time, which is why the blog post by TOR was made about it.

      •  JCPhoenix   ( @JCPhoenix@beehaw.org ) 
        link
        fedilink
        English
        5
        edit-2
        11 months ago

        Gotcha, yeah that checks out. I guess I never made that connection, even though I use TOR and torrent here and there. Probably also because I’m more concerned about download speeds over privacy when torrenting. And regular web traffic over TOR is often insanely slow compared to the clearnet.

        Ever since getting a copyright strike several years ago, I’ve switched to using a commercial VPN while torrenting. I don’t know if that’s the all-in-one solution for hiding from my ISP, but it seems to work. But I also rarely torrent these days, too, so not as many opportunities for them to catch me, I suppose.

  •  littlecolt   ( @littlecolt@lemm.ee ) 
    link
    fedilink
    English
    3111 months ago

    I pay monthly for access to a SOCKS5 proxy service from a company called BTGuard, and tell my BT client to connect through that. It is not expensive and works great I’ve been using it for about 12 or 13 years, and found it after getting an email from my ISP saying they identified me downloading TV shows. In that time, I have only had issues a handful of times. More reliable than most other services I pay for and I’ve never seen another DMCA notice since.

    •  YⓄ乙   ( @yoz@aussie.zone ) 
      link
      fedilink
      English
      0
      edit-2
      11 months ago

      What’s i2p? I downloaded i2p from fdroid and installed it. It showing peers and active peers but my IP is still the same. Can you please ELI5 ? Thanks

      •  jack   ( @jack@monero.town ) 
        link
        fedilink
        English
        1
        edit-2
        11 months ago

        I2P is a truly anonymous darknet where every user is a node in the network, unlike TOR where everyone is leeching off of the 6000 nodes. I2P also works great for torrenting. I2P is only for accessing I2P sites and not for anonymous clearnet browsing.

        I have never tried the mobile version, but here’s some info for desktop:

        There is a java version simply called “I2P” and there is a C++ one called “I2Pd”. Start with the java one, it’s easier and has built-in torrent webclient.

        Install I2P from geti2p.net and start it. You are now a node/router in the network. To access I2P darknet websites like http://planet.i2p you have to tell your browser to use I2P proxy. You should use a different browser profile for using I2P, on firefox you can create one at about:profiles .

        Enable I2P on firefox: Settings -> General -> Network Settings. Set manual http and https proxy to 127.0.0.1 port 4444 . You should now be able to visit eepsites (sites ending with .i2p). Always put http:// manually at the beginning. If it tells you to use jump services because it can’t find the site, just click on one of the suggestions.

        Torrents are on http://tracker2.postman.i2p . Find one, copy the magnet link and go to the torrent webclient: 127.0.0.1:7657/i2psnark . Add the torrent there. Done, you are now anonymously torrenting.