this post was submitted on 27 Jun 2026
219 points (97.4% liked)

Selfhosted

60810 readers
710 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] SuspiciousCarrot78@aussie.zone 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

It's probably not tenable to do this. Approx 100% of projects touch AI in some way or another. See -

https://github.blog/news-insights/research/survey-ai-wave-grows/

[โ€“] gooeyglob@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago)

"This report draws on a survey conducted online by Wakefield Research on behalf of GitHub from February 26, 2024 through March 18, 2024 among 2,000 non-student, enterprise respondents in the U.S., Brazil, India, and Germany who are not managers and work at companies with 1,000-plus employees."

I generally want to use smaller FOSS projects, and honestly dont care what tools enterprise companies are making their employees use. But I have college age children and know its being mandated there as well. Though it doesnt mean they have to use it in their own projects.

As was discussed in precious slop threads, these projects are fairly easy to identify when they get posted here, today. Sure in a year that wont be as easy, but its clear from the downvotes thrown at projects since this rule was proposed that many people here just dont want AI-written running in their self hosted systems.