Remix.run Logo
▲ figassis 17 hours ago

I build my own version, single binary that does every thing. While I built it, I learned I cannot make it open source or distribute, bc it might be illegal to do so, so I assume many people have built that, but you're always locked into the narrowly scoped lego pieces. So I enjoy my media now, without hassles, all the features I need, none I don't. I hope one day I get to share.

▲j1elo 17 hours ago | parent | next [-]

Solution is easy, in fact there are 2 solutions:

1. Clear that "might", it either is or isn't. An AI can get you 90% there, maybe the definitive confirmation would be good from a lawyer.

2. None of this matters if you share it from a foreign code forge and an anonymous pseudonym.

▲dgently7 13 hours ago | parent [-]

ianal, but presumably you could share a research document that explains the theoretical kinds of broad strokes of an all in one type system, and how youd verify it works.

if anyone decided on their own to put that it into a local model and generate their own version of something that met the theoretical spec thats their own deal...

▲figassis 9 hours ago | parent [-]

To the parent, I am not about to FAFO. To you, I am also not about to FAFO. Good luck.

▲internet101010 15 hours ago | parent | prev [-]

Same. I made the mistake of adding the downloader to it at the start but brute forced my way through. Single Rust binary for all of the *arrs + sabnzbd is nice though. Unfortunately it is not something I am comfortable making public due to the all-in-oneness of it.

Almost all of the time went to to the downloader (usenet is more complicated than I thought). If I had just focused on the basics (sonarr, radarr, seerr) I could probably could have knocked it out in a day or so.

▲Cyph0n 13 hours ago | parent [-]

It is important to point out that “a day or so” - or even the ability to spin up your own version - is only possible because these projects already exist.

Without a tested and validated reference implementation that already accounts for the numerous edge conditions and quirks of media releases, APIs, etc., your vibecoded version would have taken much longer to iterate on.

▲figassis 9 hours ago | parent [-]

That's fine, I am certain that if laws allowed, these projects would have been exactly as intended. Not their fault and nothing against them. They solved the problem the best way they could.