All I did was create a wrapper script to pipe to the torrent client, then "pipe these torrent files to the script" - so easy to circumvent you wonder why they bother
Things like when to cancel early, how to handle par2, obfuscation, rars within rars, decoding articles. Just a mountain of "huh, didn't think of that being a complex problem" that was resolved over time.
I was able to replace the arr suite + sabnzbd with my own rust+ts frankenstein but had I known how complex the usenet piece was going to be I would have separated it into two phases.
It’s not that the content is not available on the Internet it’s that it’s a better experience. Indexed high quality content that can be retrieved automatically and at high speed without the need to seed or worry about copy strikes or deal with ever changing, poor quality streaming sites.
concern from my side as well at some point, But The name comes from audio “stems” and the multitrack “deck” interface, but I understand that it can be confused with Steam Deck or Stream Deck. There is no affiliation with Valve or Elgato, and I’ll take any legitimate trademark concern seriously. Naming things really is the hardest problem in software. :)
For overall reference:
"In audio production, a stem is a discrete or grouped collection of audio sources mixed together, usually by one person, to be dealt with downstream as one unit. A single stem may be delivered in mono, stereo, or in multiple tracks for surround sound."
You don't need reverse engineering if it's publicly known fact for 20+ years, telemetry just identifies you. 20 years ago, you would need to find the printer.
reply