Comment on Selfhosted & AI - Part 2: The Results
Brkdncr@lemmy.world 3 weeks agoHow would the proposed rules help? Isnt spam already covered regardless of AI?
Comment on Selfhosted & AI - Part 2: The Results
Brkdncr@lemmy.world 3 weeks agoHow would the proposed rules help? Isnt spam already covered regardless of AI?
brucethemoose@lemmy.world 3 weeks ago
Because, with a cursory glance, it doesn’t always look like spam.
A classic example I see starts with “I built a…” in the title, has a wall of text in the description, and actually promises to do something interesting. Only upon deeply inspecting the code (or trying it yourself)… it becomes clear it’s hallucinated nonsense.
And it’s not always malicious, either. A lot of devs get deep in AI psychosis as truly believe there building something revolutionary with their vibe coding agent.
And sometimes these projects are interesting!
Hence it would be EXTREMELY helpful to have this tagged, up front. To me, an [AIP] is gigantic red flag to warrant extra caution, but not necessarily a smoking gun, and would help “regular” homebuilt projects stand out from the vibecoded ones.
And [AIT] is just nice to have. Some users don’t want to see any AI in /c/selfhosted, period. It gets reported as spam because people interpret it as that, and this gives would prevent that while giving those users a way to easily filter them out.
Brkdncr@lemmy.world 3 weeks ago
I wish the mods best of luck with implementing and enforcing this.
AI generally doesn’t need a lot of special handling when it comes to policies. It’s like any other tool, it’s just made it a lot easier for people that don’t know how to code get something made.
If anything, it might be easier for people to tag their level of experience.
brucethemoose@lemmy.world 3 weeks ago
Vibecoded self promo is a growing, specific spam problem though.
And a appreciable fraction of Lemmy/Piefed is “anti AI absolutist.”
I think that’s pretty unique.
Mondez@lemdro.id 3 weeks ago
Maybe, but even experienced devs seem to want to fall into the trap of thinking their expertise will mean they can skim review AI code and spot it’s mistakes rather than taking the time to properly review and understand the code. Low effort is low 3ffort regardless of your expertise.