CoyoteFacts

Semi-related for people whose distros don’t package deno, I installed deno in a distrobox and exported it with distrobox-export and yt-dlp picked it up just fine from my $PATH. Before I did so, running yt-dlp gave the following error:

WARNING: [youtube] No supported JavaScript runtime could be found. YouTube extraction without a JS runtime has been deprecated, and some formats may be missing. See  https://github.com/yt-dlp/yt-dlp/wiki/EJS  for details on installing one. To silence this warning, you can use  --extractor-args "youtube:player_client=default"  

I just want to note that Jellyfin MPV Shim exists and can do most of this MPV stuff while still getting the benefits of Jellyfin. You’re putting a lot of emphasis on Plex-specific limitations (which Jellyfin doesn’t have obviously) and transcoding (which is a FEATURE to stopgap an improper media player setup, not a limitation of Jellyfin).

Pretty much every single “Pro” is not exclusive to pure MPV vs. Jellyfin MPV Shim, which mainly leaves you with the cons. Also as another commenter said, I set my Jellyfin up so that my friends and family can use it, and that’s its primary value to me. I feel like a lot of this post should be re-oriented towards MPV as a great media player, not against Jellyfin as a media platform.

Yep, I forgot it’s not a company. The point stands though; someone has to pay for the servers and administration, and if they run out of money or the foundation falls apart, then the problem happens in the same way. I don’t know much about Wikipedia’s structure, but I would guess it’s a similar situation in terms of needing money to stay running and also being able to be salvaged by the community if it does go down.

Yes, it’s allowed and encouraged between RED<->OPS. There are a few tools on the RED and OPS forums to automate most of the process (e.g. Transplant, REDCurry, Takeout, Orpheus-Populator, etc.). Cross-posting torrents on many sites is allowed and fine, you just have to be aware of the rules of the source site, e.g. some places don’t want their internals to be shared, or some have a literal timer countdown before cross-posting is allowed. On the other hand, most sites are not going to enforce other sites’ exclusivity demands (PTP explicitly has a note about this). If an exclusive file is cross-posted onto PTP, PTP isn’t going to take it down on anyone’s behalf.

I’ll note that private tracker culture has warmed up quite a bit in the past decade and a half that I’ve been on them. Trackers (and their users) don’t usually see other trackers as rivals/competitors anymore, release groups are respectful of each other, there are a ton of tutorials and help forums around to help low-skill members learn how to do the advanced stuff, and so on. There are recognizable usernames everywhere, and the general vibe is to cross-upload as much as possible and help build everyone’s trackers together. Cross-seed (the program) has helped a lot with this, and seedbases have become very strong even on smaller trackers as a result.

Mainly, HDDs are bigger and FLAC is future-proof for future audio formats, as well I think the death of What.CD has really impressed upon the next generation that preservation is of utmost importance. A lot of albums were fully lost during the transition to RED/OPS, and a good chunk of albums that used to have a lossless copy now only have lossy versions from those who kept MP3 libraries. IMO, piracy is ownership, and owning the master lossless copy so you can generate any other formats is that concept taken to its logical conclusion.

Seconding the notion to get into OPS somehow if at all possible. RED’s economy is one of the few economies that is actually non-trivial, whereas OPS’s economy is totally trivial. A large amount of RED stuff is automatically mirrored to OPS, so you can just grab it at OPS and cross-seed back to RED (there are a few tools to do this automatically, e.g. nemorosa). RED is still definitely the more active and qualitative place to be, but cross-seeding shenanigans with OPS will keep RED’s economy in-check.

A lot of people just rip Qobuz, Deezer, and Tidal FLAC for free using shared keys that you can find on the megathread (“Knowledge & Tokens”). Autosnatchers will give you at least one snatch per upload. No one is actually buying most of that WEB FLAC. There also might be a big batch of freeleech tokens during December for kickstarting a library. Also, I’d recommend just going full FLAC from the start; MP3 is easier/smaller to snatch, but it’s 2025 and no one wants MP3, so long-term you’ll get the best results by perma-seeding a large FLAC library.

There’s nothing wrong with Signal’s centralization model in a worrying sense. It acts only as a clueless message relay, and it has near-zero information on any of its users, even as it delivers messages from person to person. The only information Signal knows is if a phone number is registered and the last time it connected to the server. There is great care taken to make sure everything else is completely end-to-end encrypted and unknowable, even by subpoena.

The only real issue with Signal’s centralization is that if Signal the company goes down, then all clients can no longer work until someone stands up a new server to act as a relay again. Signal isn’t the endgame of privacy, but it’s the best we have right now for a lot of usecases, and it’s the only one I’ve had any luck converting normies to as it’s very polished and has a lot of features. IMO, by the time the central Signal server turns into an actual problem we’ll hopefully have excellent options available to migrate to.

Also TMK, the only reason you still need a phone number for Signal is to combat spam. You can disable your phone number being shown to anyone else in the app and only use temporary invite codes to connect with people, so I don’t count the phone number as a huge problem, though the requirement does still annoy me as it makes having multiple accounts more difficult and asserts a certain level of privilege.