Strict3443

joined 1 year ago
[–] Strict3443@lemmy.ml 1 points 1 year ago

I'll check out MuWire, was unaware that it used DHT.

Also, I am just saying that tracker2.postman.i2p is the only torrent directory we have currently, and its best way to find and advertise torrents for others. Trackers (where your client announces to) are helpful to finding peers of the same torrent.

[–] Strict3443@lemmy.ml 2 points 1 year ago

Here is an ansible role you can use to deploy i2pd to linux servers and such: https://codeberg.org/systemfailure.net/ansible_i2pd. Otherwise, on most distros the i2pd package should be able to be installed from the package managers in the terminal.

[–] Strict3443@lemmy.ml 4 points 1 year ago (5 children)

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.

[–] Strict3443@lemmy.ml 7 points 1 year ago

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.

[–] Strict3443@lemmy.ml 13 points 1 year 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.

[–] Strict3443@lemmy.ml 8 points 1 year ago

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.

[–] Strict3443@lemmy.ml 7 points 1 year 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.

[–] Strict3443@lemmy.ml 4 points 1 year ago (7 children)

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/

[–] Strict3443@lemmy.ml 3 points 1 year ago* (last edited 1 year 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.

[–] Strict3443@lemmy.ml 7 points 1 year 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.

[–] Strict3443@lemmy.ml 8 points 1 year ago

The I2P network thanks you.

 

About

I2PSnark is an I2P-only BitTorrent client built with Java. This allows you to spin up a docker container with a I2PSnark client which can be managed through the web-ui. This specific I2PSnark application is from the I2P+ team at https://i2pplus.github.io/ and http://skank.i2p using this package http://i2pplus.github.io/installers/I2P+_2.2.0+_i2psnark-standalone.zip.

Testing

Use this .torrent file to test if your I2PSnark client is working:

http://skank.i2p/i2pupdate.zip.torrent

Find More Torrents

http://tracker2.postman.i2p (requires I2P)

 

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 ›