I asked the same question it should be tagged as [AIP]+[hint] under these rules.
hint Human acts on the task and the AI surfaces suggestions passively.
Comment on Selfhosted & AI - Part 2: The Results
Shimitar@downonthestreet.eu 1 day ago
Woah …
This is overly complex.
As a dev that sometimes published something, and I don’t vibe code butnl who doesn’t use AI nowadays? That is way too much complex. And zero projects today don’t use AI in any forms blnot even to search or bugfix …
I asked the same question it should be tagged as [AIP]+[hint] under these rules.
hint Human acts on the task and the AI surfaces suggestions passively.
To be clear only AIP would be in the title, you can mention the hint and the where in the disclosure comment
Disclosure itself is a need, and I can confidently say there are enough people who are “no ai ever”, “all ai all the time”, and “only the AI use I agree with” to make something needed.
About the only way to simplify would be to not define the disclosure types, just to disclose it, but then half the post will be discussing where and how if its not defined (along with a bunch of reports about not fully disclosing AI use).
If promo posts included that up front, I don’t think it would be an issue, but its rare that any post includes even “I used/didn’t use AI”, if that.
Shimitar@downonthestreet.eu 1 day ago Disclosure is needed, I agree.
Let’s say it feels complex, and the tags will not avoid the discussion in the comments anyway … but it’s a start so good for it
I’d love an idea to trim it down… but with the wide varieties of ways AI can be used, its hard.
I’m a good example of the “problem” person in a way. I’ll test all kinds of things (including a completely, 100% vibe coded app posted here recently…. in a sectioned off vlan of course), but what AI was used for influences where I look. Documentation? Ok, not the worst, but I’m going to check for human review/blatant llm goofs. You used it to figure out how to talk to a serial controlled endpoint? Ok, thats what needs to be checked first.
You made the whole ass thing with Claude? I’ll test it like I said, but I doubt it would ever end up anywhere near my own production use, its more as a curiosity. 99/100 that level of generated is basically the same as calling it unmaintained imo.
So there is definite value to knowing where/how/how much, and if the comments consist of things already stated and just add “slop”, thats going to get deleted, its already disclosed, the people who comment that should filter instead. Its a two way benefit this way as I see it.
That said - I’m always open to options here, but considering recent comments and reports since I’ve taken over moderating, something is definitely needed.
@curbstickle@lemmy.dbzer0.com Thanks for all that you are doing here. I want to come out and say this -even if thats not helping dicussion here. I apologize. I was part of the problem mentioned here.
I have taken down the repo, and the docker images. If I had said anything in the post that started ‘I built’ I take that back. Someone whse core value is not to dilute the truth - I missed something. Even my social post refined with AI (not a native english speaker) did credit AI. And AI usage policy, PR template with disclosure, was present in repo, took a lot of care, but I mentioned ‘not another vibe coded arr project’ the the README and then didn’t say by how much. I presumed. To me vibe coding was completely different from what I did.
I don’t want to give out my resume, or state what I did, why I did etc. I will need to say this: I like the policy laid out here and 100% make sense. I want to say I believe what you believe or even more so for a lot of reasons but then I also see various shades of grey there. It was not AI psychosis that led me to create an account and a repo like that. Also I didn’t ask for donations or ever expected one. I am sure I don’t have what it takes to maintain a linux kernel or something like curl, and not an experienced OSS maintainer. I am also not a sad AI driver without skills either. I came in without any repute, no hello nothing and dropped that recent one you likely talked about here. The product pitch wasn’t clean, the wall of text there also did not point to an easy to understand single purpose tool - it was doing many things. Looking back, it would have been infuriating to folks in that channel. Apologize again, for whatever disruption I made in the arr community from where I have taken much. Servarr had every right to kick me out… Thanks for the clarity. Grateful for the learning.
hertg@infosec.pub 1 day ago
Then this must come as a surprise to you, but I do not use “AI” whatsoever. Not for coding, not for fixing bugs, and not for coming up with concepts. Crazy right?
Not at all …
You are free to do as you please, and I fully respect that.
I was also a no AI coder, but somehow changed my mind slowly as I learned how to use PROPERLY the tool, which can be quite useful.
Learning how to use it has been fun too, so I suggest you give it a try if you haven’t done so yet.
The first risk is abusing it. The second risk is trusting it. And there are many more risks, but AI is a knife and not a pistol: there are good uses for it, but you must be careful and use it properly all the time.