this post was submitted on 23 Jun 2026
361 points (95.5% liked)

Selfhosted

60281 readers
771 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.

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
[–] meltedcheese@c.im 4 points 1 week ago

@festus @selfhosted Excellent examples. What the tag [AI] conveys is not what you really need to know, which is the quality of the code (component/unit), unit testing, and so forth. I assume there is some acceptance testing done at the project level. The human who submits the code must understand that flaws in their code is their responsibility, just as those who contribute/maintain the project are responsible at the system level. It is both an objective and reputational process. Does it really matter what tools are used if the work product passes the test, verification and validation criteria? Sloppy code is not unique to AI tools.