brickfrog

I believe because any site that has an extension with more than four characters is detected as invalid.

Usually it's just badly coded apps/websites that only whitelisted some of the main domains e.g. most vanity domains don't make it through. Or sometimes there are apps/websites that purposely block your domain if the admins think it's too spammy or whatever.

If your current email provider allows you to use their own domains as an alias that's one way to sidestep the issue e.g. you'd end up with [something]@[youremailprovider].com --> [name]@[name].rocks

I have Fastmail & they have a ton of their own internal domains so that's one way I sidestep that issue. It's pretty common among most/all email providers when you bring your own domain e.g. pretty sure Proton can do the same thing. Once you have your own domain you can make up any [alias]@[yourdomain] you like or just use the provider's as a front facing alias [alias]@[youremailprovider] --> [anything]@[yourdomain].

I don't think it's possible, or at least not in the way you're thinking. Encoding a video with lossless flags usually results in a file size bigger or about the same as the source, and on top of that it takes a long time to actually do the encode.

Video is already highly compressed.

But for sure you can tinker around with ffmpeg (FOSS) & see how it goes for you. I've done it in the past just for kicks since some of the common video codec encoders do have lossless flags but it really wasn't worth the effort.

EDIT: That's just the video in the file, you also have to contend with the audio. That's a bit easier if you just want to use ffmpeg to dump everything into FLAC but again, I don't think you're saving much hard drive space if any.

P.S I’ve enever used XD. So I can’t help you out there, but it seems like a very bare-bones torrent client. qbittorrent recently added support for it but if you’re running a headless server, XD doesn’t seem like a bad option. Github says it has no DHT support? Not sure if that’s the best option, but good luck with it.

Correct. To be fair both XD and qBittorrent don't support DHT over I2P so they're kind of on the same level there. I think (?) neither support PEX over I2P either though I'm not 100% sure on XD about that.

https://github.com/qbittorrent/qBittorrent/issues/19913

https://github.com/arvidn/libtorrent/issues/7408

https://github.com/arvidn/libtorrent/issues/7269

Currently not possible. Bitmagnet would need to have new code to be able to properly talk to the mainline java I2P service to enable DHT over I2P bittorrent. Or the Bitmagnet devs could develop their own I2P service to talk to the I2P network but that might be even more dev work.

https://github.com/bitmagnet-io/bitmagnet/issues/303

Per https://geti2p.net/en/docs/applications/bittorrent

DHT support requires SAM v3.3 PRIMARY and SUBSESSIONS for TCP and UDP over the same session. This will require substantial development effort on the client side, unless the client is written in Java. i2pd does not currently support SAM v3.3. libtorrent does not currently support SAM v3.3.

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.