this post was submitted on 07 Jun 2026
128 points (98.5% liked)

Selfhosted

59738 readers
921 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
128
Revisiting Rule #3 (anarchist.nexus)
submitted 1 day ago* (last edited 19 hours ago) by curbstickle@anarchist.nexus to c/selfhosted@lemmy.world
 

Hey everyone, as I previously mentioned the rules here are up for debate, and I'd like to start with the problem that led us all here:

  1. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

Breaking it up:

Posts have to be centered around self-hosting

Kind of obvious for the community, but perfectly fine to note.

There are other communities for discussing hardware or home computing.

Without listing anything here, I think this is pointless and unhelpful. I'd also note that hardware is intrinsic to hosting your own services, and we are talking about people hosting at home, which makes "home computing" here rather confusing. We host these things for our home computing typically. The intention I think was "This is not your generic linux help desk or buildapc", but that doesn't come through very well.

If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

I like this not from a moderation perspective, but more of a post clarity perspective. Whats obviously related to selfhosting to the OP may not be obvious to people visiting that post.

Here's what I propose as a revised rule 3:

Posts here are to be centered around self-hosting. Be prepared to explain to others why it's related to self-hosting if asked.

Please discuss! Happy to have any additional input on this.

In the meantime, I'm striking out the middle of rule 3 until there is some consensus on wording.

Edit: Its/it's typo

Edit 2: Slight language update option:

Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

you are viewing a single comment's thread
view the rest of the comments
[–] SuspiciousCarrot78@aussie.zone 4 points 9 hours ago* (last edited 9 hours ago)

Disagree with the phrasing myself.

Yes "please ensure ..." is nominally more proactive but "be prepared to explain" should force a technical framing in the first place, because the poster in on notice they may be challenged. Don't write slop, read the room etc. It also explains why the rule exists / what the fail state is.

The first one just sounds like so much corpo HR double speak.

Be bold. Say what you mean - "We talk shop here. Be prepared to put up or shut up, else bonk".

If the user can justify their question (if/when queried), it doesn't matter whether the question is hardware, software or other - it will have a grain.

Additionally it might give people an foothold into OPs thinking process / whether they selected the right room in the first place.

My $0.02 and YMMV