[-] [email protected] 43 points 1 month ago* (last edited 1 month ago)

Was MakeMKV ever claimed to be open source?

Not sure if it's exactly what you want but I've used MKVtoolnix in the past for .mkv operations, worked fine for me. And ffmpeg also works great for general audio/video stuff though I've never tried bluray -> .mkv with it.

[-] [email protected] 35 points 2 months ago

My network has reset several times and I’ve narrowed it down to an apparent DDOS attack

It's not. You will need to lower your torrent client's incoming connections limit and/or set lower limits to your incoming/outgoing bandwidth in your torrent client. It is clear your network router is unable to handle too much torrent traffic hitting it at the same time, hence the issues you are experiencing.

For qB

Tools / Options / Connection / Global Maximum Number Of Connections

Tools / Options / Speed / Global Rate Limits

There's no specific number to enter there, you just have to experiment a bit and set lower numbers until the problem goes away and your network is stable.

shutting down the client doesn’t help

It will, eventually. It does take a bit for other torrent clients to realize you're no longer online and stop sending you traffic / sharing your IP with other peers.

[-] [email protected] 41 points 3 months ago

Again with this? You're just spamming /c/Piracy at this point (and probably breaking rule #4).

[-] [email protected] 36 points 8 months ago* (last edited 8 months ago)

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.

[-] [email protected] 49 points 9 months ago

Maybe you meant Reddit admins?

Reddit moderators don't have access to IP addresses nor have the ability to ban someone based on an IP address.

[-] [email protected] 30 points 9 months ago

Just to clarify OP is referring to sharing invites in [email protected]

[-] [email protected] 49 points 10 months ago* (last edited 10 months ago)

I have a 13 series chip, it had some reproducible crashing issues that so far have subsided by downclocking it.

From the article:

the company confirmed a patch is coming in mid-August that should address the “root cause” of exposure to elevated voltage. But if your 13th or 14th Gen Intel Core processor is already crashing, that patch apparently won’t fix it.

Citing unnamed sources, Tom’s Hardware reports that any degradation of the processor is irreversible, and an Intel spokesperson did not deny that when we asked.

If your CPU is already crashing then that's it, game over. The upcoming patch cannot fix it. You've got to figure out if you can do a warranty replacement or continue to live with workarounds like you're doing now.

Their retail boxed CPUs usually have a 3(?) year warranty so for a 13th gen CPU you may be midway or at the tail end of that warranty period. If it's OEM, etc. it could be a 1 year warranty aka Intel isn't doing anything about it unless a class action suit forces them :/

The whole situation sucks and honestly seems a bit crazy that Intel hasn't already issued a recall or dealt with this earlier.

[-] [email protected] 36 points 1 year ago

Fastmail is great but it's a totally different market /use case, you wouldn't go with them if you're privacy oriented. They're better than Google in that sense but you'd go with Proton if you're looking for privacy features.

Also keep in mind Fastmail is based in Australia and their government tends to be anti-privacy with the laws that get passed there.

[-] [email protected] 36 points 2 years ago* (last edited 2 years ago)

I’ve been considering moving to Jellyfin for a while, but I’m worried they will do the same thing in future.

Currently would not be possible. Jellyfin does not have the sort of centralized accounts/logins that Plex does e.g. you're not asking Jellyfin devs for permission to log into your own server. That's just a Plex thing.

If you're asking could they add that "feature" in the future? Highly unlikely but I guess anything is possible. Were that to happen most likely the code would get forked into a new project.

PS - Jellyfin itself is a fork from Emby back when those devs decided to close their source. Myself & tons of other people dropped Emby at that point & migrated to Jellyfin. https://jellyfin.org/docs/general/about/

[-] [email protected] 37 points 2 years ago

Lemmy world is turning into Reddit v2

Not really, even Reddit still has piracy related subreddits (at least for now).

[-] [email protected] 36 points 2 years ago

No according to admin, see the comment thread in the other post

https://lemmy.dbzer0.com/comment/399136

[-] [email protected] 31 points 2 years ago

Is it really crucial to find a VPN that supports port forwarding?

It is not required but you will have a much better torrenting experience by being connectable (port forwarded). When you are fully connectable you are able to make direct connections to all peers in torrent swarms so overall your upload/download speeds would be faster and you can still participate in small torrent swarms.

When you are firewalled (not port forwarded) you can only make direct connections to peers that themselves are connectable (port forwarded).

In practice when you are in large torrent swarms it may not make much difference, there's often plenty of connectable peers in large torrent swarms that you can connect with. However in smaller torrent swarms if no one is connectable then all the firewalled peers can only see each other, no data will transfer. They are all stuck waiting for a connectable peer to join the swarm & help with the data transfer.

view more: ‹ prev next ›

brickfrog

0 post score
0 comment score
joined 2 years ago