brickfrog

And it’s like 3-4 hundred ish.

That should be easy for just about any torrent client (including Transmission), could be worth opening an issue at their GitHub page https://github.com/transmission/transmission/issues

Hopefully switching torrent clients resolves that for you.

I’m migrating because Transmission is horrible for a large amount of torrents (multiple of hundreds)

That doesn't sound like too many, you're saying you're at under 1000 torrents? How many multiples of hundreds are we talking?

Surprised Transmission has issues seeding that many, thought Transmission 4.x made improvements in that area. How much RAM does your system have? Maybe at some point you just need more system resources to handle the load.

PS - For what it's worth you can still stick with Transmission and/or other torrent clients & just spread the torrents among multiple torrent client instances. e.g. run multiple Transmission instances with each seeding 1000 or whatever amount of torrents works for you.

It's a nice gesture but I'm a bit doubtful that there's enough people here to sustain a private tracker. Taking a guess at this but it seems most people here in c/piracy are general users, not specifically private tracker users - in fact a fair amount don't even like the idea of private trackers.

!trackers@lemmy.dbzer0.com exists but it's pretty quiet by comparison.

Not saying it's a bad idea but it could be a while before a niche tracker like that would gain enough traction to sustain itself. And I'm just talking about a regular private tracker, not even going to touch on the idea of someone developing a "decentralized private tracker" whatever that means.. TBH if you want decentralized just stick to public torrents with DHT/PEX, that's already decentralized. Or maybe make a semi-private tracker like Demonoid if that's more along the lines of what you want.

Not overly active but you could sub/participate in

!opensignups@lemmy.ml

!opensignups@noworriesto.day

Also !torrent_trackers@lemmy.ml (it's more of a tracker listing community)

And right here in dbzer0 there's !trackers@lemmy.dbzer0.com for general discussion as well.

EDIT: For specific sites / non-Lemmy you can monitor https://opentrackers.org, I kind of wonder if the admin ever made it over to Lemmy. On Reddit he goes by cuddlebunny and an earlier nick IIRC (but that's all ancient info now probably).

This way, private torrents could “escape” into the wild, still maintaining the privacy and social/closed community effects of the private tracker.

Except that it wouldn't. The infohash that the private flagged torrent generated is different vs a public non-private torrent of the same contents. Your suggestion would purposely share the same exact private torrent infohash into public DHT/PEX, that would certainly get people banned at the source private tracker(s). I also suspect most/all torrent client developers would consider that incorrect behavior.

If you wanted to do a more "correct" approach on this - Create a brand new public non-private flagged torrent of those contents, which would generate its own unique infohash, then it's just a regular torrent. You'd end up needing to seed multiple copies of the same torrent (the original private flagged torrent and your new public torrent) but sure that would be possible as long as the torrent client itself has DHT/PEX enabled. Most private trackers won't care too much but some of that does depend on individual trackers and uploaders, you'd need to check their rules.

If it's a movie blu ray you can usually play the "index.bdmv" file in a compatible media player e.g. VLC definitely works. MPC-HC / MPC-BE works too, I think(?) MPV can play them too. As well as Jellyfin and Kodi if that's your thing.

Alternatively browse into the "STREAM" folder, usually the biggest .m2ts file in there is the actual movie or whatever it is you want to play. The above media players can play that directly if preferred.

For TV series the above usually works too but the episodes are usually split out among multiple .m2ts files so it might be easier just to play them directly in that case.

Jellyfin should work fine for what you're looking for. I haven't run it on a Pi but it should work on that. You'll be able to play music using the web ui as well as mobile apps if that's your thing. It can also transcode on the fly so if your current browser/device/whatever can't play .flac directly it'll automatically transcode the playback to .mp3 or whatever it needs to be.

There are some other self hosted music/streaming projects you could take a look at that are much more built out for music playback specifically. Look into Airsonic-Advanced or Navidrome for example - I've been meaning to check them out myself but haven't gotten around to it yet.

Maybe private trackers? I'm not a member at these but TVCUK ~~and TheEmpire~~ do tend to get mentioned as trackers with that type of content.

EDIT: TheEmpire apparently does not include UK in their torrents per the other comment.

Does p2p over i2p require port forwarding?

No, you'll torrent fine via I2P without port forwarding. Note that the torrents are running through the I2P network so technically you wouldn't want to open your torrent client to the clearnet anyway. It'd be like purposely introducing a VPN leak in your VPN setup by allowing it traffic outside the VPN (or in this case I2P).

Been a bit since I've tinkered with torrents over I2P but for a while I was seeding torrents over I2P and would get pretty good seed/upload speeds to other torrent peers. Was mainly testing with i2psnark and BiglyBT.

Fun fact: Torrent hashes don't change, so that same exact torrent you might download at TPB or wherever would still download within I2P as long as there's someone seeding it there.

Also see https://geti2p.net/en/faq#ports

Not exactly what you're asking but you can open a port forward for I2P itself to better communicate with other I2P routers. "routers" in this case usually means other people running I2P.

I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?

Correct. You're referring to the thin client, offhand I think it's just Transmission and Deluge that have that. You don't need a thin client for a headless torrent client setup, plenty of people do fine with a web ui. But I get it, if you prefer using a thin client then yeah Deluge or Transmission are your options for that.

re: Deluge once you have logging enabled it'll be easier to troubleshoot things. Always seemed a bit odd that Deluge doesn't at least enable error/warning logging by default but that's a Deluge thing.

The behavior isn't normal - Without the error message itself it's hard to say. You're not seeing any tracker errors or anything like that within Deluge right?

Otherwise shut down Deluge, enable logging, then re-start it. See "Enable Deluge Logging" in https://deluge-torrent.org/troubleshooting

Maybe you want to set the log level to "error" or "warning", if those don't yield anything new then set it to "info" to log whatever error it is.

Also maybe update your post with your OS and Deluge / LibTorrent version.

For what it's worth in the past I've sometimes seen Deluge error on a brand new private tracker torrent, sometimes the private tracker needs a few seconds or a minute to update the tracker and show seeds/etc. - in those random cases Deluge ends up talking to the private tracker before all that & that results in it displaying some error like torrent not found at tracker, I forget exactly what the error was. It's a bit odd since I've never seen rTorrent/ruTorrent have that issue, seemed like a Deluge thing. Been a while since i've dealt with that and can't remember how I fixed it, think it involved having a delay before Deluge attempted to load/start the torrent.

for headless you get either Deluge or Transmission

The paid Seedbox providers usually default to rTorrent/ruTorrent for headless torrenting on their Linux based systems. Deluge/Transmission are the alternative clients in those cases.

Nowadays qBittorrent with webui enabled behaves pretty well on a headless system otherwise qbittorrent-nox is also an option.

Ah yes I think you're right, good catch. There isn't any distinction between a regular account vs uploader, they just use their skull system to denote "trusted" uploaders.