Yup, I'm posting another this week. Sorry.
This week I'm hoping we can wrangle a solution around AI and our selfhosted community. There are plenty of strong opinions (both pro and con), but one thing is for certain - there needs to be better disclosure in promo posts. Two options (that aren't mutually exclusive):
- Any posts of an AI focused, AI Developed, etc software gets an [AI] tag. No, a [Not-AI] tag is not needed to accomplish this, thats kind of a "non-golfer" sort of tag.
- Comment requiring an AI disclosure response to every promo post, if its not detailed in the post itself. Specifics (generating docs for commands, translation, whole-boat vibe-coded this app, etc) would be requested.
I will say that having disclosure and/or tagging would mean that comments that just say "slop" or "fuck ai" or whatever would be off topic at that point, that information is already provided, so its just noise (and sometimes pretty uncivil - I've been light on that for now due to the need for a rule on this).
The tag [AI] would make it easy to filter out (or search for, if that's your thing), but there is a wildly different degree of AI use out there, and from the posts with a positive score, its usually due to responsible AI use (translations, a snippet they had to do something obscure with, available to use with AI but doesn't require it, whatever), which is why I think the disclosure has a place as a benefit to everyone.
Please provide any input or alternative options on this, and I can then put it to a vote like the last one. Comments seem to be the best approach without involving something off-site, but if you have a better idea/option, please share.
So when I write code, I regularly ask an LLM how to do things. A few examples from my history is how I could overlap rows when generating PDF files (have a library for this), how I could assign an empty Char and to create a singleton class. A LLM never changes any of my files, I use it as super-search-engine.
Would that constitute an AI tag?
Yes, because it is a bit different than a search engine. It may not be changing the files, but it is telling you the way to do it. It might give you an outdated method/pattern, it might ignore conventions, and most importantly, it doesn't really understand the problem its solving. Its not finding the optimal answer, its finding the most common.
So the resulting answer may work, but not necessarily be right. In a disclosure (see the new thread) that would be referred to as "hint" for lllm use.
That doesn't mean the answer you got was necessarily wrong either, just an answer based on an amalgam of the most common for all the code fed into the model, no matter when the code was written.
It would be put into an ai disclosure, so it qualifies for a tag. Make sense?
Makes sense, thanks for taking the time to explain. <3