this post was submitted on 19 Feb 2024
0 points (NaN% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55064 readers
153 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

At least in arch, the package qbittorrent-nox now contains the ability to connect to i2p. For people starting out, using i2p you wouldn't need to use a VPN to download your favorite "linux ISOs"; just use i2p and have a fully automated Jellyfin server!

I recommend using i2pd as the i2p router

top 8 comments
sorted by: hot top controversial new old
[–] RyeMan@lemmy.world 1 points 10 months ago* (last edited 10 months ago)

qBittorrent I have not tried personally but I would think that if you have i2p set up on qbit already then enabling the setting "automatically add these trackers to new downloads" and add in a few open i2p trackers. Postman requires an account so unless the exact same torrent has already been posted there you won't be able to bridge.

For Prowlarr, it's a little more complicated. You can add Postman just like any other indexer but you then need to configure your proxy settings in Prowlarr for it to be reachable. If you are running your i2p router on the same machine you can just enter your local address (127.0.0.1) with port 4444 and it'll connect. If your router is on a remote machine the easiest solution is to then use ssh port forwarding (autossh is handy here). Ssh forward the remote 4444 port to local and then use the same address and port. The final step is setting your ignored addresses, I have a bit of a list but the idea is to filter out all non .i2p addresses so an example would look like: *.com, *.net, *.info, ......

EDIT: I should also add, if you are sticking with I2PD and are more concerned with just downloading and not incorporating the *arr suite there is a standalone Snark download that's floating around somewhere that can plug into I2PD. I haven't used the standalone personally but I do know that Snark is by far the most optimized client exclusively for i2p torrents. Snark is also baked into the standard i2p install by default.

[–] GravitySpoiled@lemmy.ml 0 points 10 months ago* (last edited 10 months ago) (1 children)

Does it work for the average joe?

If not, what's missing such that we all can move to it?

[–] aldalire@lemmy.dbzer0.com 0 points 10 months ago (1 children)

It's all free and open source! If you're on windows it might be a little more difficult so at least having a linux PC you can reliably have on 24/7 would make things easier. I personally use arch (I've tried this on my endeavour OS), very easy installation for beginners) for this since it's rolling release (latest versions of packages!) and the AUR is a godsend. The programs themselves take little ram and cpu, with qbittorrent probably needing the most ram once you have more torrents downloaded (I'm running this on 4 cores of CPU and 4 gigs of ram alongside my minecraft server, a tor relay and a monero node. any old laptop repurposed with endeavour should do the trick)

the steps I took to do this (on endeavour os) was:

install i2pd

  • sudo pacman -S i2pd

Install qbittorrent webui

  • sudo pacman -S qbittorrent-nox

install prowlarr (optionally sonarr and radarr, which will automatically manage video files for you. Plays reaaaally well with Jellyfin, so you wouldn't have weirdly formatted files that is being read by Jellyfin)

  • yay -S prowlarr
  • yay -S sonarr
  • yay -S radarr

Lastly you have to turn enable the *arrs in systemd

  • sudo systemctl enable --now prowlarr
  • (do the same with sonarr and radarr if you have them)

(or you can also go the docker route with qbittorrent, prowlarr, sonarr and radarr, if you don't have arch. This is the more universal route and can handle many more devices. Although I have not checked if qbittorrent-docker has i2p integration yet. For that you may need to swap out qbittorrent for vuze, or apply the patch in the comment in the link i posted in the docker container [which is editing the qBittorrent.conf file])

For the average joe i'd say it'll be an afternoon's worth of labor to set up, and the upside is not relying on a VPN to install content and a fully automated Jellyfin server! Plus you get to help the steadily-growing i2p network If you have more questions I'd be happy to answer here :)

[–] UntouchedWagons@lemmy.ca 0 points 10 months ago (1 children)

So how does one actually use I2P?

[–] aldalire@lemmy.dbzer0.com 1 points 10 months ago

if you install java i2p it should come with the browser and torrent client (i2psnark) pre-packaged

for i2pd (c++ implenetation) you have to configure firefox (i use librewolf with noscript) to use the http proxy (on port 4444).

[–] Nerrad@lemmy.world 0 points 10 months ago (2 children)

Wouldnt it a take a month to download a Linux ISO over i2p?

[–] aldalire@lemmy.dbzer0.com 1 points 10 months ago

I'd wager around 2 hours once the router has been running for a day or so.

[–] CAVOK@lemmy.world 1 points 9 months ago

Currently testing it. 20 peers. 1.5GB. Takes about 20 min.