Strict3443

joined 2 years ago
[–] [email protected] 13 points 2 years ago

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.

[–] [email protected] 7 points 2 years ago (2 children)

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.

[–] [email protected] 4 points 2 years ago

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/

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago)

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.

[–] [email protected] 7 points 2 years ago (3 children)

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.

[–] [email protected] 8 points 2 years ago

The I2P network thanks you.

[–] [email protected] 4 points 2 years ago

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

[–] [email protected] 3 points 2 years ago

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.

[–] [email protected] 3 points 2 years ago

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

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

[–] [email protected] 2 points 2 years ago

Glad to see that working still! Torrenting over I2P is sort of a fail-safe option for people in somewhat oppressive places where VPNs may be illegal. Also, with the recent port-forwarding removal in Mullvad, this makes it harder moving forward to try and seed content without being able to make a direct connection with open ports.

 

cross-posted from: https://lemmy.ml/post/4912475

https://codeberg.org/Strict3443/qbittorrent-i2p-vnc

I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.

In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.

Why?

I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my linuxserver/qbittorrent docker container and it just works.

Why don't you post the docker image?

I am not sure how yet, and I also left it as a Dockerfile so that you can build this on ARM or x86-64 depending on your needs

Note

This image can be quite heavy and take a long time to build, but until v4.6.x is out of beta, this will do.

 

https://codeberg.org/Strict3443/qbittorrent-i2p-vnc

I have created a Dockerfile which will compile the latest version of qBittorrent which has experimental I2P support into a docker container with VNC support. The reason for this is my server is headless and I wanted to use the v4.6.x version of qBittorrent, but the qbittorrent-nox version of v4.6.x does not have I2P options yet. So I had to build the GUI version on top of a VNC image.

In doing so, this will build a container that has VNC capabilities where you can utilize a desktop environment to setup the GUI version of qBittorrent with your I2P settings, and then just use the web-ui from there on.

Why?

I am a qBittorrent user and wanted to start downloading and cross-seeding torrents with I2P, so I built this image as a drop in replacement of my linuxserver/qbittorrent docker container and it just works.

Why don't you post the docker image?

I am not sure how yet, and I also left it as a Dockerfile so that you can build this on ARM or x86-64 depending on your needs

Note

This image can be quite heavy and take a long time to build, but until v4.6.x is out of beta, this will do.

view more: ‹ prev next ›