I've seen this "consolidate all the arr" attempts for many years now. None prevail. Not saying this one won't, but something tells me it's going to peter out and be abandonware. It's incredible how still the OG arr apps have been to be honest. Likely because they are extremely stable and well-integrated.
I would use it for a regularly scheduled validation job.
Sometimes a bad copy, mismatch, or low-rated media slips through all the filters. Could use an LLM to fix the media and harden the filters to prevent issues going forward. I’ve probably spent weeks of my life toiling and tweaking over the last 15 years.
Not the OP, but I see a lot of complaints on HN about dumb media player "voice control". I myself had cringe experiences with my car when I wanted to play a particular genre or song.
This interests me, but I’ll let it cook a bit more before I give it a spin. I’ve got enough customization that moving to this without disruption may be a little challenging, or token heavy.
Adding a “Copy prompt for agent” instruction to the top of your docs, would be lower friction to entry, and allow me to review what it is that needs doing. It can be hard to account for every way someone might self host in docs too, which is why I think an agent is going to have a much easier time automating the setup here.
What do you mean "for now" if there's one thing i don't want it to replace it's clearly qbittorrent. Trackers have client whitelist and I don't see a brand new vibecoded app being added to any of the serious ones
Ok, I'm a potential user, but what is your long term plan for following the scene and making sure HolyArrs supports the wild west of the grey area content acquisition?
Things like parsing the file name for format, group, language, repack etc...
Subtitles? I really don't want to sign up to Opensubtitles and be hit with their ridiculous daily limit (on what is just text).
I was looking for a project just like yours and couldn't be bothered building one myself.
Edit: Gemini has provided some subtitles options.
Subtitle Search & Database APIs
• TheSubtitleDB.org: A completely free, open REST API for media players and apps. It requires no account, no API key, and has no rate limits, offering exact file hash matching as well as IMDb ID and TV episode lookups.
• Wyzie Subs (wyzie.io): A fast subtitle search API for movies and TV shows. It offers a free tier with 1,000 requests per day, sub-50ms response times, hearing-impaired filter options, and multi-language support.
• Opensubtitles-Unofficial-API: An open-source, community-hosted unofficial API. It lets you search and download subtitles from OpenSubtitle.
I don’t get this. So today he can build the experience he wants with little effort (he likely spent lots of tokens). You made no judgement in the quality or on his experience, only on the age of the repo. Why exactly is that?
I get there will be a lot of crapware, but you’re hackers no? Why all the gatekeeping even amongst yourselves? How much time did the openclaw guy take to built it? A weekend?
Sure, you could say “no thanks”. But all the labs certainly thought it was useful enough to replicate. And yes, it was, still is an insecure mess littered with bugs, but why are we all so repulsed?
It’s a genuine need. I build my own version of this, also on go, haven’t shared bc I am not sure how legal it is to distribute, but I have been using it for months and definitely beats running 6+ apps that keep breaking. I run one binary + jellyfin, never going back.
The problem is not the vibecoding, it is the release of a public facing internet app that is not a day old, hence it is impossible to know if it has security issues. He is supposedly a security engineer and he RELEASES a repo with less than a day old? how do you know it is secure? Again, this is something that will interact with the open internet.
Gatekeeping would be "do not write vibecoded apps for yourself", which is not the case here, this is releasing code for the public in an irresponsible manner.
I believe things will be from now on. People see a gap in the offerings out there and they just whip it up. There will be a certain amount of stability that the LLMs will add by default to all of them and that's it. If you are interested, go ahead and use it.
I create my own vibecoded apps for my own use, that is not the problem. releasing them for others (who might not know this hasn't been tested) is irresponsible.
hi HN, im luis. 10+ years in software and security, homelabbing for about 5
"netflix and spotify" is how it feels to use, not what it does under the hood. holyarrs doesnt play anything. you browse your shows, movies and music like a streaming app (top 10s, new & popular, coming soon), tap what you want, and it sends it to your downloader and files it into jellyfin or plex. those still do the playing
before this, my server needed 6 apps for that: sonarr for shows, radarr for movies, lidarr for music, bazarr for subtitles, prowlarr for indexers and overseerr for requests. 6 setups, 6 databases, and nobody in my house but me could use any of them
- the image is 15 MB. the 6 apps it replaces are 718 MB together
- one go binary, svelte UI, sqlite. the image has no OS and no shell
- runs on amd64, arm64 and armv7
- works with qbittorrent, sabnzbd, plex, jellyfin, emby
- imports your sonarr/radarr setup, and speaks their api so seerr can keep talking to it
- no api keys to set up. posters and search come from a metadata server i run and pay for
- free, AGPL-3.0
how it got built: claude code wrote most of the go and svelte. i wrote the specs, reviewed everything and tested it on my own server. what it got wrong: it never noticed cost. the app got heavier build after build until i started measuring every single one. thats the only reason its still 15 MB
why you might want to wait: its young, 1.0.7 shipped today and im fixing reports as they come in. music is still being built out, and a few features are held back until theyre fully tested (plex watchlists, trakt lists, subtitle sites)
why i built it: my family wanted netflix and i had 6 apps nobody but me could use
I'm interested. Does it handle subtitles translation with AI ? This is a must have for me.
First try to obtain subtitles in the locale I need, fallback to using AI to translate the embeded ones, fallback to downloading ones in original language / english and translating.
Why would you even want this, what desirable features could you add by adding AI?
Sometimes a bad copy, mismatch, or low-rated media slips through all the filters. Could use an LLM to fix the media and harden the filters to prevent issues going forward. I’ve probably spent weeks of my life toiling and tweaking over the last 15 years.
Adding a “Copy prompt for agent” instruction to the top of your docs, would be lower friction to entry, and allow me to review what it is that needs doing. It can be hard to account for every way someone might self host in docs too, which is why I think an agent is going to have a much easier time automating the setup here.
Though I like the choice of go. The heavy c# stack other have is quite resource intensive
https://www.reddit.com/r/selfhosted/comments/1rckopd/huntarr...
What do you mean "for now" if there's one thing i don't want it to replace it's clearly qbittorrent. Trackers have client whitelist and I don't see a brand new vibecoded app being added to any of the serious ones
Things like parsing the file name for format, group, language, repack etc...
Are you aiming to be more feature complete with the rest of the *arr stack or intentionally a different course?
I was looking for a project just like yours and couldn't be bothered building one myself.
Edit: Gemini has provided some subtitles options.
Subtitle Search & Database APIs
• TheSubtitleDB.org: A completely free, open REST API for media players and apps. It requires no account, no API key, and has no rate limits, offering exact file hash matching as well as IMDb ID and TV episode lookups.
• Wyzie Subs (wyzie.io): A fast subtitle search API for movies and TV shows. It offers a free tier with 1,000 requests per day, sub-50ms response times, hearing-impaired filter options, and multi-language support.
• Opensubtitles-Unofficial-API: An open-source, community-hosted unofficial API. It lets you search and download subtitles from OpenSubtitle.
I get there will be a lot of crapware, but you’re hackers no? Why all the gatekeeping even amongst yourselves? How much time did the openclaw guy take to built it? A weekend?
Sure, you could say “no thanks”. But all the labs certainly thought it was useful enough to replicate. And yes, it was, still is an insecure mess littered with bugs, but why are we all so repulsed?
It’s a genuine need. I build my own version of this, also on go, haven’t shared bc I am not sure how legal it is to distribute, but I have been using it for months and definitely beats running 6+ apps that keep breaking. I run one binary + jellyfin, never going back.
Gatekeeping would be "do not write vibecoded apps for yourself", which is not the case here, this is releasing code for the public in an irresponsible manner.
I believe things will be from now on. People see a gap in the offerings out there and they just whip it up. There will be a certain amount of stability that the LLMs will add by default to all of them and that's it. If you are interested, go ahead and use it.
"netflix and spotify" is how it feels to use, not what it does under the hood. holyarrs doesnt play anything. you browse your shows, movies and music like a streaming app (top 10s, new & popular, coming soon), tap what you want, and it sends it to your downloader and files it into jellyfin or plex. those still do the playing
before this, my server needed 6 apps for that: sonarr for shows, radarr for movies, lidarr for music, bazarr for subtitles, prowlarr for indexers and overseerr for requests. 6 setups, 6 databases, and nobody in my house but me could use any of them
- the image is 15 MB. the 6 apps it replaces are 718 MB together - one go binary, svelte UI, sqlite. the image has no OS and no shell - runs on amd64, arm64 and armv7 - works with qbittorrent, sabnzbd, plex, jellyfin, emby - imports your sonarr/radarr setup, and speaks their api so seerr can keep talking to it - no api keys to set up. posters and search come from a metadata server i run and pay for - free, AGPL-3.0
how it got built: claude code wrote most of the go and svelte. i wrote the specs, reviewed everything and tested it on my own server. what it got wrong: it never noticed cost. the app got heavier build after build until i started measuring every single one. thats the only reason its still 15 MB
why you might want to wait: its young, 1.0.7 shipped today and im fixing reports as they come in. music is still being built out, and a few features are held back until theyre fully tested (plex watchlists, trakt lists, subtitle sites)
why i built it: my family wanted netflix and i had 6 apps nobody but me could use
im in the comments, tell me what breaks
First try to obtain subtitles in the locale I need, fallback to using AI to translate the embeded ones, fallback to downloading ones in original language / english and translating.
That’s how I feel. I’ll give this a try.
I'm not convinced this is true, could you expand further what you mean here?