What @[email protected] said. Basically you get access to the I2P network (overlay on top of the regular internet) that provides anonymity and doesn't require any port forwarding. Thus, this allows every user to seed torrents without worrying about opening ports or getting letters in the mail.

The torrent space on I2P is still growing, there are some chads cross-seeding to the I2P network allowing for torrenting popular torrents over I2P.

It is experimental indeed. While it "works", it is no where near the reliability and efficiency of other I2P torrent clients like I2Psnark or BiglyBT, both of which are Java based.

That is the lacking area. There needs to be a development in the area of DHT crawlers and indexers to help find torrents on I2P like how btdigg works, but for I2P torrents. Hopefully one day.

notbob.i2p and identiguy.i2p have been my go to as they provide uptime stats and show the reliability of that eepsite. Seems like many people set up a registered eepsite just for testing or the short-term and don't intend for longevity, but you can find some eepsites with normal names like "git.idk.i2p" and assume it will have better uptime.

Eepsites that provide similar "stats" can be found here: http://notbob.i2p/cgi-bin/defcon.cgi?category=stats

"Alive" hosts can be found here: http://reg.i2p/alive

Guide for Linux: https://strict3443.codeberg.page/i2p-info/hugo/public/posts/how-to-use-i2p-on-qbittorrent-nox/

You can install i2pd with sudo apt install i2pd and then point your services towards your i2p router (Ex. 127.0.0.1) and you are good to go.

Yes, I did exactly this when I2P support was first in beta. I have a docker stack with Gluetun as my network for all my *arr containers and I was able to still point my qBittorrent to my i2pd router and it worked just fine.

Yes, absolutely. I have a VPS that runs a i2pd router and I can set my clients to point to my VPS and I am able to use the I2P network. In doing so, I had to make sure I forwarded the correct ports on my VPS so that it would reach the i2pd application. I will do a write up soon.

The I2P network thanks you.

Careful copying the 5th one. Markdown caused it to render the URL differently.

This should force the correct URL to render:

http://lnQ6yoBTxQuQU8EQ1FlF395ITIQF-HGJxUeFvzETLFnoczNjQvKDbtSB7aHhn853zjVXrJBgwlB9sO57KakBDaJ50lUZgVPhjlI19TgJ-CxyHhHSCeKx5JzURdEW-ucdONMynr-b2zwhsx8VQCJwCEkARvt21YkOyQDaB9IdV8aTAmP~PUJQxRwceaTMn96FcVenwdXqleE16fI8CVFOV18jbJKrhTOYpTtcZKV4l1wNYBDwKgwPx5c0kcrRzFyw5~bjuAKO~GJ5dR7BQsL7AwBoQUS4k1lwoYrG1kOIBeDD3XF8BWb6K3GOOoyjc1umYKpur3G~FxBuqtHAsDRICkEbKUqJ9mPYQlTSujhNxiRIW-oLwMtvayCFci99oX8MvazPS7~97x0Gsm-onEK1Td9nBdmq30OqDxpRtXBimbzkLbR1IKObbg9HvrKs3L-kSyGwTUmHG9rSQSoZEvFMA-S0EXO~o4g21q1oikmxPMhkeVwQ22VHB0-LZJfmLr4SAAAA.i2p/announce.php

You can cross-seed torrents by adding I2P trackers to the tracker list. What helps is when you upload the .torrent file to tracker2.postman.i2p (the only? i2p public torrent tracker) so that others can find the magnet/torrent link and start downloading. That way people can find the InfoHash and also have trackers embedded in the i2p .torrent file to allow you to find seeders.

Some info on this subject: https://old.reddit.com/r/i2p/comments/xfqvap/how_to_correctly_cross_seed_to_make_clearnet/

What I mean is if I create a new torrent of Big Buck Bunny with a InfoHash of b1946ac92492d2347c6235b4d2611184 for example, no one will find my torrent by searching for "Big Buck Bunny". Unless I post this hash somewhere, advertising "Hey, this torrent is Big Buck Bunny" like what 1337x and other torrent sites do, you won't "find" it. Basically, we have to use a torrent indexer like tracker2.postman.i2p to search the metadata and find torrents we want. If that makes sense.

https://geti2p.net/en/docs/how/threat-model#sybil

Good write-up from the I2P team on this topic. Page includes other attack vectors as well.

The most known outproxy: https://stormycloud.org/i2p-outproxy/

You can try using BiglyBT on android following these instructions: https://github.com/BiglySoftware/BiglyBT/wiki/I2P#user-content-biglybt-i2p-and-android

Otherwise, I'd suggest using a desktop to run i2psnark, BiglyBT, or qBittorrent and use i2pd along with those clients.

From my experience, some popular I2P torrents have gotten up to 1 MB/s download, but I usually average around 200 KB/s. While it is not blazing fast, it does provide a good deal of anonymity for everyone involved with the torrent.

Yes, I believe that the Syncthing protocol doesn't bring security concerns, but some people may wish to hide their IP and device info from being "exposed". I know Syncthing has some data collection which you can opt out of.

I think a benefit of this post is to show that you can self-host applications and use the I2P network to connect to your services while bypassing issues like CGNAT. Hopefully, it helps spark ideas to host more services on I2P as well.

Piped Link: https://piped.kavin.rocks/watch?v=VHmJP19gHAo

Invidious Link: https://yewtu.be/watch?v=VHmJP19gHAo

https://geti2p.net/en/download for the java version, which comes with extra apps. Otherwise, you can go to https://i2pd.website/ for the C++ version which is much lighter and you can just point your browser/torrent clients at the i2p router and you are good to go.

CPU: remove AVX code, switch to __builtin for AES detection #1959

https://github.com/PurpleI2P/i2pd/pull/1959

That is i2p-java and i2p+ only. i2pd is only the router which is why it is so small and fast.