this post was submitted on 19 May 2024
53 points (96.5% liked)

Selfhosted

40359 readers
304 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hey selfhosters!

I recently discovered Tribler - anonymity focus torrent client. It made some rounds on hackernews and I'd never heard of it before.

I installed gui and was not impressed - it ran terribly on macos. However, I was able to test download and its anonymity features - it uses TOR inspired onion routing. I saw they had API available - and thought it would be perfect for my selfhosted *arr stack usage. However, *arr apps did not integrate tribler API (understandably, it's a niche client)

I dug in a bit and thought it would not be so difficult to create a shim that pretends to be some better integrated torrent client.

I picked qbittorrent.

You can check the link. I run it in docker. Add it to sonarr / radarr as qbittorrent client (username and password is irrelevant, as tribler shim integrates with tribler through API key) It's not the most secure approach - but managing torrents wihout authentication in my home network is an acceptable risk.

I was not able to download anything with more than 1 hops in between - ie it does hide your real IP address, but only uses one relay in between. It's not perfect, but seems to work as designed. I run my services mostly in Kubernetes, so there's likely something in my networking that. I will poke around more to see what could be the issue.

For now, the torrent management works through arr apps using the shim, however, the category is not implemented. Therefore, you can only use one category for both sonarr and radarr for example, and you will see downloads of both of those.

you are viewing a single comment's thread
view the rest of the comments
[–] sashka@lemmy.ml 4 points 6 months ago (1 children)

Nice, thanks for pointing this out! I think you're right, 1 hop is direct to exit nodes, which is quite weak for anonymity.

[–] brickfrog@lemmy.dbzer0.com 2 points 6 months ago* (last edited 6 months ago)

True, wouldn't be too different vs just using a VPN. You're choosing to trust the Tribler tech and the Tribler exit node operator vs choosing to trust the VPN provider. Granted most VPN connections are going to have much better performance vs anything Tribler related.

There is a nice side effect of running an *arr stack against Tribler, even in 1 hop mode - Your Tribler node is much more easily pulling in new content into the Tribler network for other users to access afterwards without needing an exit node. Ideally it's just one Tribler node/user needing to pull data through the exit nodes while the rest would just pull it from you and share with other nodes in-network.

Torrents over I2P work the same way. If the torrent data isn't found within I2P and you have outproxies configured you could pull torrents from the clearnet & afterwards other I2P users just share amongst the I2P network.