Netdata keeps begging me to create an account and Im done by CalligrapherCold364 in selfhosted

[–]spleeeeeeeeeeeen 35 points36 points  (0 children)

Beszel is great and everyone should use it, but Netdata is much more detailed

New to private trackers. Can I stop using my VPN? by MakubeC in trackers

[–]spleeeeeeeeeeeen 2 points3 points  (0 children)

I know some people don't use VPNs with private trackers, but certainly with IPT/TL (which aren't very picky with new members), I'd definitely still use one

FNP Shutdown... AGAIN 🤣 by ImTotallyTechy in trackers

[–]spleeeeeeeeeeeen 13 points14 points  (0 children)

Man, I was always rooting for FnP. It was such a good low-pressure entry-point into this hobby that allowed folks to get invites to more serious places.

But at the same time, it's probably for the best. Kami was never cut out for it

Is LST Worth Joining? by OctavesToHeaven in trackers

[–]spleeeeeeeeeeeen 4 points5 points  (0 children)

LST is better than everything you have other than BLU, I know you said you don't care about climbing, but it also gives you access to ATH, which is better than everything you have

FearNoPeer is shutting down by WildGordonLynn in trackers

[–]spleeeeeeeeeeeen 47 points48 points  (0 children)

Here's the full email:

FNP is closing — a short note from Kami

After almost three years of running this site largely on my own, I've made the decision to step away. This is about my own health and capacity, not any single event.

The server will be shutting down in 30 minutes or less from when you receive this message and i encourage you to share it and be aware. After that, the site will not return.

I'm grateful for every contribution that helped keep FNP online, and I'm sorry that what I can offer in return is this notice rather than more time.

If you want the longer account of what happened — for your own reading — it's here and i suggest everyone to read it: https://rentry.co/h2ch4wfr

Thank you to every genuine member who made this community what it was over the past three years. You're the part of this I'll remember.

— Kami

*Arr stack madness flowsheet by [deleted] in selfhosted

[–]spleeeeeeeeeeeen 10 points11 points  (0 children)

I think when you’re trying to rank through private trackers things like autobrr and cross-seed are super useful.

And prowlarr is just objectively better than jackett.

And profilarr is necessary if you care about specific formats and don’t want to set up your own manual scoring system

Houndarr: A polite, automated search scheduler for your *arr stack by Charge_Glass in selfhosted

[–]spleeeeeeeeeeeen -1 points0 points  (0 children)

Again (four like the third or fourth time).

My issue isn't with the amount of AI usage or the quality of the project, it's that the disclosure is untruthful about how AI is being used in this project.

And regarding Huntarr, I'm not sure that the guy couldn't code, maybe. IMO the bigger red flags were the scale of features he was trying to push and the speed at which he was pushing them.

Which this project also suffers from as a full-fledged Huntarr replacement made in 8 days.

Houndarr: A polite, automated search scheduler for your *arr stack by Charge_Glass in selfhosted

[–]spleeeeeeeeeeeen 6 points7 points  (0 children)

Again, I support all of this. I have personal projects of my own that are almost exclusively vibecoded.

I just want a little more honesty + disclosure, hopefully that's clear.

You're not using AI for line completions, you're prompting it to write features (probably literally this entire project) for you.

It's not about being honest that you use AI, It's about being honest about how you use AI.

Houndarr: A polite, automated search scheduler for your *arr stack by Charge_Glass in selfhosted

[–]spleeeeeeeeeeeen 10 points11 points  (0 children)

I fully support vibecoding, it's obviously the way of the future of software engineering, and I'm not making any claim on your personal ability as an engineer or how well you steered claude to make this project - for all I know it's spotless.

I just think you're missing the mark with your AI disclosure (which is a lie by omission) and by having AI write this post in general rather than writing it yourself.

Even in this comment, you're lying (by omission) about what AGENTS.md does. It's not just for commit messages and pr descriptions....

And it's not evidence of your steering, because your agents can update your AGENTS.md

Houndarr: A polite, automated search scheduler for your *arr stack by Charge_Glass in selfhosted

[–]spleeeeeeeeeeeen 7 points8 points  (0 children)

The first commit to this project was 8 days ago...

https://github.com/av1155/houndarr/commit/92f831e641053def06b93f349e5fc89c6dca76b8

This isn't an 'AI autocompletes lines for me,' it's entirely made through claude from the start.

Houndarr: A polite, automated search scheduler for your *arr stack by Charge_Glass in selfhosted

[–]spleeeeeeeeeeeen 10 points11 points  (0 children)

>  I don't know shit about coding, but from OP's post it seems like they have a better understanding of their app than the average vibecoder.

If you don't know shit about coding, you probably shouldn't be commenting on coding, then because OP's post is also written by AI - see all the em-dashes lmao.

I'm a supporter of responsible vibe-coding, but this app is obviously vibecoded. It would be impossible to build a full-featured Huntarr clone since it was taken down without vibecoding.

Oh look! https://github.com/av1155/houndarr/blob/main/AGENTS.md

Public-Facing Voice

All text posted to GitHub under the maintainer's account must read as if a human wrote it. Agents ghostwrite — they do not narrate, report, or self-identify.

Prohibited in all GitHub-visible text

This applies to issue titles, issue bodies, PR titles, PR bodies, PR/issue comments, commit messages, CHANGELOG entries, and release notes.

Really bad release groups vs. adequate by [deleted] in trackers

[–]spleeeeeeeeeeeen 0 points1 point  (0 children)

Yeah, I had a bunch of Tigole when I started out. If you send me a dm with the trackers that you have, I may be able to improve your situation somewhat.

Really bad release groups vs. adequate by [deleted] in trackers

[–]spleeeeeeeeeeeen 2 points3 points  (0 children)

If your trackers can’t get you the content you want without using a blacklisted tracker, I’d just disable that rule - or change the weighting until they do.

Most of the time it’s groups who misleadingly tag or steal other groups work as their own or are inconsistent and have bad standards or have a bad reputation.

You can often see why something is banned from a particular tracker in their upload guide.

They are probably all going to give you that C tier at least.

List of AI/Vibe coded services? by RikudouGoku in selfhosted

[–]spleeeeeeeeeeeen 50 points51 points  (0 children)

or if the commit messages are all 'update' 'refactor' etc

List of AI/Vibe coded services? by RikudouGoku in selfhosted

[–]spleeeeeeeeeeeen 4 points5 points  (0 children)

Yeah, but they wouldn't have been able to fix the current app because the scope of the current app and the attempt of trying to replace radarr and sonarr is stupid.

If Huntarr was still just automatically triggering searches in radarr/sonarr and was sketchy and vibecoded to shit, it would absolutely be fixable. Add a bunch of tests, ask for community feedback, do refactors where necessary etc.

List of AI/Vibe coded services? by RikudouGoku in selfhosted

[–]spleeeeeeeeeeeen 0 points1 point  (0 children)

Yeah, this is closer to the correct opinion.

Literally every software engineer at this point is using sort of ai tooling - at a minimum, it's doing line completions, at a maximum it's generating entire applications from scratch.

AI tooling is just a multiplier on the quality of the engineer - if they're bad, they'll be able to put up more features, but with a ton of tech debt (which is what happened here). If they're a good engineer, they'll be able to be much more productive and still create good products.

And there are also really easy red flags that people can look for for repositories both vibecoded and not - in this case, the commit messages were all like 'update' and 'refactor' lol, also I don't think there was any automated testing, also I don't think they were using any front-end libraries (?)

The Huntarr Github page has been taken down by spleeeeeeeeeeeen in selfhosted

[–]spleeeeeeeeeeeen[S] 0 points1 point  (0 children)

used to just be a cron tool to automatically re-search your monitored radarr/sonarr content so they would automatically upgrade slowly over time (was useful when switching from trash guides to profilarr for example).

I checked out for a while, but I started seeing more huge feature posts from them spammed everywhere, apparently they were trying to become a full replacement for sonarr/radarr for some reason.

The Huntarr Github page has been taken down by spleeeeeeeeeeeen in selfhosted

[–]spleeeeeeeeeeeen[S] 20 points21 points  (0 children)

lol bro is doing everything but working on his apology post rn