~~@frey@lemmy.world please update with the appropriate tag per rules 7/8~~
Thanks
Its a pretty big stretch to call this self-hosting related....
Locking the thread.
September 23rd, fyi
Thats about all that we can control on this side, though. It would be great if more people made use of https://ai-declaration.md/, its what the rules here are (mostly) based on for disclosure, but half the time even a proper readme is more than what a repo will contain.
At least as a post here we can address appropriately.
Having a discussion on this is perfectly fine, but I want to remind of two things.
Lets keep it friendly and constructive.
but i will only hate/judge/completly ignore programms/tools/documentation thats clearly vibecoded slop.
If its disclosed and tagged, then keep that thought to yourself - its now OT (rule 3) or potentially a rule 1 violating comment depending on how its phrased. In either case, its not appropriate for the post.
If its not disclosed and/or tagged, report it.
Don’t disclose - slop
"Don't disclose" means report, not commenting.
Disclose with AIP - not specific enough, still assume slop
Not specific enough because it requires a disclosure, any comments of "slop" should be reported not interacted with.
Disclose more specifically - “slop”
"Slop" with an appropriate disclosure is a rule 1 violation. Report.
Disclosure is for the post, not comments.
If you see it in comments but not in a post, report it. Not comments, but reporting, otherwise its just more cleanup later.
Please add your disclosure. See rule 8. Locking for now + cleanup.
What I might consider is a "winterized" variable per hose/pipe that may be a concern, and only notify if winterized is false for those, and have the notification list specifically not winterized.
That state would be manual per, but then you would be able to get a more meaningful reminder to only those that would be at risk.
No worries!
All set thanks!