Script was fixed and now correctly copies the reseed certificates from the repo to the data directory. Running the script on a fresh alpine container now results in a working i2pd router with no config necessary. This fixes the "Firewall Status: Unknown" issue.
Here is a relevant guide: https://geti2p.net/en/about/browser-config
For the IP address, just put in your container's IP address instead of 127.0.0.1
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.
This is a good point. I also feel like private trackers are meant for people who actually seed content they download, and just have good intentions to help share content. This also comes with hardware requirements (disk space) sometimes that not everyone has.
It would be nice to have qBittorrent auto add I2P trackers to all torrents to help cross-seed them.
The most known outproxy: https://stormycloud.org/i2p-outproxy/
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.
Also, you can lower the anonymity and increase speeds by reducing the number of hops from 3 to 2 or 1. You can choose how "anonymous" you'd like to be while torrenting, at the cost of speed.
Same. There just needs to be better support for I2P in the various torrent clients. i2psnark is the "best" option I have used, but wow is it heavy and clunky. Hoping for better support in qBittorrent soon.
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.
CPU: remove AVX code, switch to __builtin for AES detection #1959
Piped Link: https://piped.kavin.rocks/watch?v=VHmJP19gHAo
Invidious Link: https://yewtu.be/watch?v=VHmJP19gHAo
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.