this post was submitted on 23 Jun 2026
273 points (95.7% liked)

Selfhosted

61004 readers
229 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
 

Based on recent comments this feels like a discussion we should have. So..topic, basically.

I'm not looking to be chief noisemaker on this, but I stand by what I wrote in !privacy and what's in my post history.

https://lemmy.ml/post/48724623/26190950

Let's have at; do we want a [AI] and [NOT AI] tag. Why or why not?

you are viewing a single comment's thread
view the rest of the comments
[–] Pika@sh.itjust.works 1 points 1 month ago* (last edited 1 month ago)

the only way they could prevent that was to mandate that disclosure had to be in the post body somewhere and not the title, that way it only appears once someone opens the post. Mostly because some posts are visible from feeds other than subscribed which means that members would see it that are outside of the normal/average visitors here.

Honestly I think i would prefer that. Instead of requiring a tag, require AI disclosure on the project somewhere in the post body.