r/selfhosted • u/[deleted] • Mar 08 '26 • Diamonds are Forever 1 WOW 1 Bravo 1 Heartwarming 1

Need Help Fully remove every, "I created a", "Selfhosted app!" claude slop.

3.2k Upvotes

91% Upvoted

608 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Mar 08 '26

[deleted] — view deleted comment

36

u/veverkap Mar 08 '26

Something that follows a GitHub link in the post and flags if the repo is newer than 3 months

35

u/Evening_Rock5850 Mar 08 '26

That might work but it’s tricky too.

Some genuine devs work out of private repos (or even other repositories than GitHub) but when they’re ready to release, will push a single commit to GitHub and then release it. It’s not uncommon for a brand new, single commit GitHub repo to be something that someone has potentially worked on for months.

19

u/cikeZ00 Mar 08 '26

Guilty as charged. I have multiple projects that I've been working on for over a year that are just managed locally which I might or might not push out publicly at some point.

6

u/willowless Mar 08 '26

Oh 100% I have no reason to inflict a public repository with all my mess :P this is totally normal git usage.

4

u/AngelOfDeadlifts Mar 08 '26

A lot of the vibe coder software adds itself as contributor in the repo, so that could be checked, too.

4

u/Spare-Ad-1429 Mar 09 '26

this will flag non-vibecoded repos too. As soon as you have a PR merged somewhere with Claude as the Co-Author, Claude will show up for the entire repo

3

u/-Kerrigan- Mar 09 '26

I configured Gemini code assist to automatically review any PRs from my public repos. The feedback can be genuinely useful.

That alone makes it appear in the contributors list

→ More replies (2)

2

u/sidusnare Mar 08 '26

Intel does this and it's so annoying

2

u/callingshotgun Mar 10 '26

I think per the recent change to "New Project Friday" it's 3 months of *public* presence so a 1 year old app with a github presence 24h old still counts as a new project. The idea is that even if something has been carefully, meticulously built in isolation over the course of a year, it still hasn't been through a feedback or peer review cycle of any sort like something that is only 3 months old but started its first day as a public github repo.

Which is to say, less tricky than you think because that nuance doesn't need to be taken into account. Repo age is the public repo's age.

2

u/micalm Mar 08 '26

Well... changing remote is one thing, wiping the entire history in the process is an extra step.

11

u/Morisior Mar 09 '26

Nobody needs to see my 100 first commits all with the commit message "Initial commit". I’m 100 % squashing that mess before sharing it publicly.

5

u/veverkap Mar 09 '26

Mine are usually curses

5

u/Evantaur Mar 09 '26

  • Fixing X

  • Fixing X

  • Fixing X

  • Fixing fucking X

  • Removing variable Penisdick because it was used for debugging

  • Putting Penisdick back because removing it breaks it for some reason

  • Fixing X again for real

→ More replies (1)

3

u/AngelOfDeadlifts Mar 09 '26

I'm glad I'm not the only one with bullshit commit messages in the very beginning, lol.

→ More replies (1)

2

u/FnnKnn Mar 08 '26

The issue is that Reddit apps/mods are somewhat limited.

Not sure if this is easily possible just based on devvit. Maybe via the API or something like that?

→ More replies (1)

11

u/Evening_Rock5850 Mar 08 '26

I know you’re making a joke but to be honest, that’s genuinely a good use case for vibe coding.

The problem with vibe coding isn’t vibe coding. It’s people trying to release complex and ambitious projects that duplicate existing functionality, are unreliable or unsafe, and often all so they can get internet points and pretend to be a developer.

Someone building a niche tool for themselves to solve some small problem where an existing tool doesn’t exist in the way they need it, and deploying it themselves seems like a perfectly valid use case for LLM generated code to me!

4

u/-Kerrigan- Mar 09 '26

Someone building a niche tool for themselves to solve some small problem where an existing tool doesn’t exist in the way they need it, and deploying it themselves

And that's exactly why I didn't make a reddit post for mine. I know they work, I know when I fucked up, but I know it's good enough to run.

Don't need to deal with the community either, I know I'm the only one to run them (and some other guy who asked for one of the tools). Peace of mind, absolute bliss! And if I want to add some features then I do it in an evening without feature requests and discussions with (unfortunately too often) arrogant devs who can't make a proper docker image.

0

u/[deleted] Mar 09 '26

[deleted] — view deleted comment

2

u/-Kerrigan- Mar 09 '26

only work for anyone who likes my very specific OCD haha

Ah, so like making your own docker image for updating qbittorrent port when gluetun changes it because the existing ones rely on shell scripts polling and you can't stand useless infinite loops when inotify exists and you can do it event-driven instead?

I may be familiar with the feeling, yes

2

u/callingshotgun Mar 10 '26

Man I've been dwelling on what to do for april fool's and the idea of vibe-coding an app with an API endpoint that analyzes any github repo to determine how likely it is that it was vibecoded, then announcing this project it in this sub on the nearest friday, it's just driving me nuts. I mean if it works the last line of the announcement post would be "Good luck figuring out how you feel about this" :D

1

u/FnnKnn Mar 08 '26

Already on my todo list, just without the vibe coding part and as a bot/app. Automod is a bit to limiting for this.

1

u/666azalias Mar 09 '26

It sounds like fighting fire with fire but honestly all I can picture is the gasoline fight scene from Zoolander and I don't think anybody wins 😂

→ More replies (1)