So -
There’s no disclosure OP could have made that you would have accepted in good faith then? And “just do it yourself” - you mean like OP did with AIP?
Weird logic, friend.
When it comes to AI hysteria, Lemmy reminds me of the movie Chinatown.
“Forget it, Jake. It’s Chinatown.”
Could be worse. I had some muppet following me across three communities telling people not to use my “AI slop” project (begrudgingly shared by request) after I disclosed AIP.
You’re fine. Next time don’t use punctuation and formatting in your blurb - less attack surface :)
This is a deeply unserious take.
Assuming the worst when someone has proactively disclosed is a strange way to encourage disclosure.
You admit to having no way of checking. Fine. So, if OP hadn’t in good faith used AIP, or had taken a millisecond to add agents.md to .gitignore, you wouldn’t have known - and you’d have had nothing to say.
Again, agents.md is not an indicator of vibe coding. If the entirety of your due diligence is spotting that file or running slopscan, we’re better off not tagging at all.
The position you’re defending punishes honesty and rewards non-disclosure. That’s not a reasonable default. That’s backwards.
[AIP] doesn’t imply vibe coded. It came out of community consensus to signal use of AI tools at any stage of the development cycle.
The presence of agents.md likewise doesn’t imply vibe coding. It’s an open standard (now under the Linux Foundation) for giving AI tools project-specific context.
It’s a configuration file for your tooling, not evidence the AI wrote your code.
FWIW, calling something vibe coded when it isn’t is a slur in dev circles.
OP cleanly announced AIP.
Treating that as equivalent to vibe coding is a category error
They went from $0 to 2x$0.
Outrageous, really.
PS: It’s a joke; user above is making a joke about plex vs jellyfin price increases.
This any good?
Probably not, no.