curbstickle

Hey folks!

I've started up a wiki for the community here, putting it up on Codeberg for easy access, edits, and forking if desired.

Right now you'll see only three pages:

• Home: A quick landing page and overview, with a link to external resources that matches the sidebar here.
• Glossary: Overview of terms~~, which I just realized has a few formatting goofs I'll be fixing shortly.~~ Edit: Fixed
• OS Choices: A review of how to choose your OS for self-hosting, or multiple if thats a better fit for your needs.

There is also a hidden _Sidebar.md, which is visible as a sidebar on the wiki. There you'll see the framework of what I'm setting up, and the links are put in only when the content is there.

A few notes:

• This is all my brain dump at the moment. I'm trying to keep personal opinions / slant out of it, but some things may still show up. Most likely unintentional, so it can be addressed if you see it.
• I use Kate for all of my editing, and the preview is.... eh not my favorite, so its absolutely possible for me to notice formatting snafus after a commit. As mentioned above. As always, you can feel free to comment, contribute, correct, etc.
• Codeberg wiki has a few... specific limitations, notably that everything goes into the same directory. Subdirectories are only for assets, so you may see names have a common theme, like "getting_started_WhateverTheActualPageIs". This is intentional for my sorting purposes to deal with how they handle things.
• I've seen someone here share their wiki for a user (who I'll be reaching out to), as I'd personally enjoy seeing members of our community featured as a resource. If you have a wiki you'd like to share, please send me a message. If the list gets lengthy, we can turn it into a link to a post called Community Member Knowledge Base or something.
• The repository above the wiki has things like the rules and sidebar contents, minus a few of the more recent things like the example post. I add there as I have time available, and a bit of a python script for a super basic bot will be there as well (to respond to [AIP] posts without a Disclosure, have to make a few fixes on that before it goes in)

After I get the getting started section complete, I'll add to the sidebar as a resource, but I wanted to put this out there if others wanted to contribute as well.

---

Edit: Kind of stretching the definition of "code", but I've added the tag since this is kind of a promo item.

---

Edit: Now with a hardware section - once I add in the writeup for services (at a getting started level) it'll be in the sidebar fulltime. A tomorrow task if I can swing it...

Hey everyone! There have been a bunch of comments lately, all basically the same with the same link, and all coming from lemmy . 1095 . me.

If you see a comment from an account there, please report it as spam and don't bother with a reply.

This is not a real post, but several examples of a self-promotion post that would need to meet the requirements of rules 7 & 8. The links will all go to the wiki I've started on Codeberg. While none of it was created with an LLM, its being used as a sample link.

These are the categories for a disclosure. Only those with AI assistance (at any level) get listed.

• Design - architecture, system design
• Implementation - production code
• Testing - writing tests, test plans, and QA.
• Documentation - Docs, comments, README, change logs
• Review - Code review and pull request feedback
• Deployment - CI/CD configuration.

Each category that uses AI is then shown, along with the level of AI involvement. There are four levels of AI support to then use:

• Hint - AI suggested solution, human does the task.
• Assisted - AI acts on part of a task, but a human handled the bulk.
• Pair - About a 50/50 split of human made and generated.
• Generated - Human prompted, AI generated.

A few different examples are shown below

---

Example 1 - A human prompted, and AI generated everything

I made a thing! It does stuff, and you can find it at codeberg. Its open source, and since my account is more than 30 days old I can post about it here!

AI Disclosure:

• Design - Generated
• Implementation - Generated
• Testing - Generated
• Documentation - Generated
• Review - Generated
• Deployment - Generated

Since AI generated everything from a prompt, and each category is involved in my fake project, all categories are displayed

---

Example 2 - Mixed levels of AI use for the entire project, except for the Design (architecture/system design)

I made a thing! It does stuff, and you can find it at codeberg. Its open source, but there is a paid subscription component. My account is more than 30 days old and I regularly post and comment without promoting my project for at least 90% of my posts/comments, so I can post about it here!

AI Disclosure:

• Implementation - Generated
• Testing - Hint
• Documentation - Pair
• Review - Assisted
• Deployment - Generated

As the design came entirely from a human, it does not need to be listed. Everything after that though involved AI, so they do need to be listed.

This tells the community that the implementation (code) and deployment (CI/CD pipeline) were entirely handled by AI from a prompt.

For testing, I asked AI for the best way to handle it, but implemented the test plans, tests, and performed the QA myself.

The documentation was about a 50/50 split on effort, because I used AI to generate the readme, changelogs, and some of the general documentation, while the rest of the documentation and all of the comments were handled by a person.

Review (code review / pull request feedback) was mostly handled by a person, but still involves AI in some of the effort.

---

Example 3 - I used AI to help me work with a piece of hardware over a serial connection, and nothing else

I made a thing! It does stuff, and you can find it at codeberg. Its open source, and since my account is more than 30 days old I can post about it here!

AI Disclosure:

• Implementation - Hint

Note: I only used AI to figure out how to communicate with this weird device I bought from a garage sale and couldn't find any documentation on the protocol.

Since I only used AI to figure out how to talk to the device, and through that series of AI prompts I came up with the code for the communication protocol which I then wrote entirely myself, only Implementation is listed.

Since it was such a small part, I decided to note how I used it, both to show that this came mostly from me, but also by mentioning it this is where folks may want to pay attention if they want to contribute. Someone may be familiar with the device I found at a garage sale, and has a printed copy of the 40yr old manual that includes the protocol.

---

Example 4 - I used AI in some way, but I've already made that clear in the git repository with an AI declaration file.

I made a thing! It does stuff, and you can find it at codeberg. Its open source, and since my account is more than 30 days old I can post about it here!

AI Disclosure can be found in the git repository here.

Since I've already created an AI disclosure document in my repository, I don't need to declare it again here. Instead, I can link to that disclosure for everyone to easily find and get the full details.

---

Hopefully this helps clear up any confusion around how to make an AI disclosure. If you have any questions please feel free to message before posting.

Comments are disabled, to start a discussion with the community about this post or the rules in general, please make a meta post. Please stick to one specific item to address as your post to keep discussions on topic.

Due to the large number of AI-involved projects, posts oriented towards AI use on a self-hosted system, and the widely varied sentiment around AI usage, an additional rule has been created to manage them.

If your post is about AI or is a project promotion post, please read here first. If you are not posting about AI or making a project promotion post, you don't need to read further.

If a post has tagged with an AI tag, low effort comments regarding their use will be removed.

Post Tagging

There are three types of tags for project promotional / AI posts.

• [CBH] - Code By Human - A project promotional post with a project that did not use AI in any capacity. No disclosure necessary.
• [AIP] - AI Project - A project promotional post with a project that used AI in development in any capacity. Disclosure is required for how it was used.
• [AIT] - AI Topic - A discussion topic that includes AI. This may be for a discussion on hardware to self-host on, llama.cpp vs ollama, your experience using vulkan, etc.

[AIP] - AI Project Disclosure Requirements

Declaration structure is a modified version of ai-declaration.md. If you are promoting a project where AI was used in any capacity in the creation of the project, you will need to provide the details of its use. If you already have an ai-declaration.md or similar disclosure in your repository, you may link directly to it. If you do not, use the following structure:

Declare what aspect of the project used AI. You only need to provide the categories where AI was used:

• Design - architecture, system design
• Implementation - production code
• Testing - writing tests, test plans, and QA.
• Documentation - Docs, comments, README, change logs
• Review - Code review and pull request feedback
• Deployment - CI/CD configuration.

Then state the level of AI involvement for each category listed:

• Hint - AI suggested solution, human does the task.
• Assisted - AI acts on part of a task, but a human handled the bulk.
• Pair - About a 50/50 split of human made and generated.
• Generated - Human prompted, AI generated.

If you have used the [AIP] tag without a disclosure, a comment will request it. Please note that failing to provide the disclosure will mean the removal of your post.

For any questions, please send a message for clarification.

With the overwhelming majority in support, the rules have been updated and will go into effect today.

Sorry it took an extra couple of days folks! My servers handled the storm well, despite the power companies' best efforts, but the outages made delaying the update a bit more sensible.

---

As a review, I want to highlight the constructive feedback:

• Overwhelming majority support some kind of tagging to identify AI projects and discussions
• A small portion have mentioned a preference for a "Not AI" tag, specifically for project promo posts to make it an active choice
• Too many tags would make it too complicated
• A tag for AI topics as well as a tag for AI projects would be helpful
• A variation of [AI] is preferred by folks who commented on tag naming
• A tag is not enough, how they used AI is important
• A tagged post should not have drive-by comments that don't add to the conversation

For those who want "no AI ever", that isn't really possible. I'd recommend starting a new community, as so many critical pieces use AI in some capacity (linux, openssl, mariadb, curl, node, go, etc) that it would be a very different, hyper-specific community.

---

My recommendation based on what was said:

• Three tags:
  • [CBH] - Code By Human - A promo post with a project that did not use AI in any capacity.
  • [AIP] - AI Project - A promo post with a project that used AI in development in any capacity. Disclosure is required for how it was used.
  • [AIT] - AI Topic - A discussion topic that includes AI. This is for items like "I want to customize a model to evaluate fish happiness based on CV captures" or "I'm having trouble configuring this MCP"

Posts that are not promotional and do not involve AI would not require a tag.

All promo posts would require a tag, making it an active decision to put [CBH] or [AIP], and would become kind of an extension of rule 7.

For [AIP], there would be a disclosure followup. I'm thinking something akin to the candor.md/ai-declaration.md approach, and this structure is based on that. The poster would need to identify which part of the process used AI:

• Design - architecture, system design
• Implementation - production code
• Testing - writing tests, test plans, and QA.
• Documentation - Docs, comments, readmes, changelogs
• Review - Code review and pull request feedback
• Deployment - CI/CD configuration.

And then the level (human only elements can be skipped):

• Hint - AI suggested solution, human does the task.
• Assisted - AI acts on part of a task, but a human handled the bulk.
• Pair - About a 50/50 split of human made and generated.
• Generated - a human prompted, the llm generated. (I see no substantial differentiation between Copilot and auto from ai-declaration.md for our use case, so I renamed to 'generated')

The requirement would be to call out only the parts which used AI, and the level of AI involvement for that process. So lets say there was an post tagged [AIP], and lets also assume there was a working automod to make this comment:

---

It looks like you've posted a project with the [AIP] tag.

Please reply to this comment with your AI Disclosure as described in the [AI RULES POST] (this will be a link), required for all [AIP] posts.

Identify which parts of the process involved AI (Design, Implementation, Testing, Documentation, Review, Deployment) and the level of AI involvement (hint, assist, pair, generated). See the [AI RULES POST] for details. Additional notes on use are welcomed if you'd like to provide them.

---

The [AI Rules Post] would contain the details above, just like the expanded rules post/explanations.

Failure to provide a disclosure after using the tag would mean removing the post. It could be locked, but I would have to assume the majority of the spam-type postings that happened to make it past the rule 7 criteria are the ones who will not provide the requested disclosure. I think it makes for a good filter this way, but please comment if you think otherwise.

In terms of timing, I'd say an hour should be more than enough time to provide a reply. If there isn't one, then the post should be reported so it could be removed. Removals, as always, will be by a person, so they will be at some point after the hour limit.

I'll likely make a crappy little bot in python to handle the tag check, check post_id to make sure it hasn't already replied (this way if it gets edited in it will still comment) specifically for the [AIP] tag only. It won't do a single thing otherwise. If you know of an existing (and good) bot for this, please share, or be subjected to the roughly 50 lines of code I wrote this morning. If I do use mine, I'll put it up on codeberg so everyone can see exactly what its doing.... and then get mad and tell me there is a better way.

Speaking of, I've made a repo for /c/selfhosted, currently with just the detailed rules post. I'll put other information there later, such as the AI rules post, the comment bot (if applicable), etc. This will also go into the sidebar once I've had time to update the README and other details.

Please respond with your questions, comments, and criticisms

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.

Post history:

• July 7, 2026: Rule 8 added, rule 7 updated to include AI-related rules.
• June 27, 2026: Initial post creation.

---

In an effort to make the sidebar a bit cleaner, and allow for more thorough explanation of the rules, this post has been made. Comments are disabled, to start a discussion with the community about this post or the rules in general, please make a meta post. Please stick to one specific item to address as your post to keep discussions on topic.

If you see a rule violation, please report rather than interacting with the post/comment.

Rules:

1. Be civil.

This is a community of collaboration. We aren't here to put each other down, but lift each other up - helping to improve efficiencies, find the right solution to deploy, or work through bugs.

Disagreement and strong opinions are welcome, being degrading or disrespectful is not.

A good reference would be the Lemmy.world Terms of Service as well as the ACoC.

Sexism, racism, ethno-supremacy, homophobia, slurs for ethnicities, genders, sexualities, etc, will not be tolerated. If you see it, report it. Don't interact, as the comment chain will likely be nuked.

2. No spam.

Spam is not “I don’t like this”.

Spam would generally be considered:

• Mass-posting - Posting the exact same post across a bunch of of different communities, rapidly. Cross-posting is not spam, but cross-posting to communities where it wouldn't fit, is.
• Repetitive Content (aka karma farming) - repeatedly submitting old popular content. This is completely irrelevant on Lemmy,, but the behavior is still not permitted.
• Bot Activity / AI Abuse - Using scripts/bots/gen AI to automate posts and comments.
• Unsolicited DMs - Mass private messages or chats to users, completely unsolicited

Bots are allowed, but see the Rules of Use for Bots on Lemmy.World, where this community is located. Please be sure to review these rules prior to using a bot in this community.

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

Please ensure it is clear in your post how it relates to self-hosting.

If you see a post where there is a more appropriate place for the discussion to take place, such as a linux or networking community, please feel free to recommend it to the user as well as report.

From a community discussion on this rule:

• Posts that are better off in a different community (not just intent, but also a community thats appropriately supported by activity) will be locked only after that community is noted. Posts will not be deleted though, only locked.
• If there is an influx of simple posts about hardware, pictures of setups, etc., then we can go ahead with a weekly sticky for that content.
• Low effort content is currently well managed with upvotes and downvotes. If there is an influx of low effort content, we can use a different approach.
• Repeated common questions, once enough of them are being seen, will go to an FAQ post or a wiki.

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

If everything you're posting is in the link, there isn't much value to adding that text. If you're going to add text, make it contextual. Summarize it, mention why selfhoster's might be interested in the news link, how you're using this software, etc.

5. Submission headline should match the article title.

Add supporting or related information in the post itself rather than the title.

6. No trolling.

Trolling is deliberately posting something offensive, nonsensical, or provocative to bait people into arguments or to get an emotional reaction. Its disruptive and manipulative, and is not permitted here.

A few key characteristics:

• Baiting: Comments / posts to make people angry or confused
• Derailing conversations: Ruining meaningful discussions by steering them off topic

Downplaying this behavior by claiming it was "just a joke" will not impact moderation decisions. See rule 1.

7. Promotion posts require your active participation in selfhosting or related communities, and your account must be at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See this link for further details.

• Your promotional post must be appropriately tagged, and AI usage disclosed. Refer to AI & Promotional Post Expanded Rules for further details.
• Active participation is defined by the 10% rule - no more than 10% of your posts or comments may be self-promotional, or your post will be removed. That is not per-project, but your account as a whole. If the entirety of your post and comment history is your blog and projects, then your post history is entirely self-promotional.
• Account Age has been added as a requirement to mitigate frequent posts that were being seen within the community. This rule applies in all cases, whether you intend to post about a paid or F/LOSS project. There are no exemptions from this requirement.
• F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from the 10% requirement. The exception does not exempt you from the account age requirement.

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.

This post will receive updates as rules are updated.

Edit 3:

So 0 and 1 have essentially no support, while 30 day has twice the support of a 7 day account age requirement...

I'm going to have to say the 30 day account age requirement takes it, update to the rules coming.

Given the length of things, I'm also preparing a "rules explanation post" (that will be locked from comments only to keep it clean), to allow the rules list in the sidebar to be shortened up. Meaningful details will be in the post, and comments are - as always - welcomed, either direct or via meta post.

Thanks all for bearing with me in the first few weeks of changes!

---

Edit 2:

I think the "no minimum" and "1-day minimum" are pretty clearly not going to take the lead at this point, but "no minimum" has a whopping 0 upvotes.

That does not mean that votes are closed!

Please continue to vote. I'll give this a full 24 hours, but in the interest of the community preference I'm going to clean up the past 24hrs worth of posts now, and put the 7 day minimum into the rules as a starting point while we give folks an opportunity to provide their up/downvotes.

---

I worry this is going to turn the rules into needing a post with full descriptions, but in the interest of the fun being had this week...

I think a mandatory delay on posts for new accounts doing promo, even if they are fully f/loss, can stem the tide.

I'm going to make comments below as a quick poll below for timeframes. Please upvote the ones you'd be ok with, downvote if you're against it. Since this will be quick I'm going to keep comments closed for now - if you have comments please add them to the main thread.

Edit: For the record I've removed the initial upvote from myself by creating the comment, so the net on each is exactly as the community votes on each item.

Edit 4:

This has more than substantial community support, and is being put into effect immediately.

Please bear with me on the sidebar edit, as I'm not going to be in front of my PC for a bit.

As previously mentioned this will remain up for the week to allow for refinement for edge cases if possible, and be aware I'm trying to see what I can do to make this more of a direct vote on specific options going forward. If anyone believes this needs revisiting after the week is up, please feel free to start a conversation on it.

May your latency be low and your uptimes be high!

---

Edit 3 - further refining.

There are some rather... unique interpretations of what a promo post is, along with an important note that some people lurk. Its important though that they participate somewhere to make sure its not a drive-by ad, but its fair to say that there are users in programming, linux, and other communities whose posts would be welcomed by users here.

Its also important to users here that its not just post and disappear.

So I'm adjusting to:

Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from this rule as long as you continue to engage in comments.

---

EDIT 2 AT THE TOP AGAIN:

It seems there is some confusion around the term "promo posts", so I'm making another adjustment for clarity. If this is muddying the waters instead, please point that out!

Self-promotion posts advertising their product requires community participation, or they will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from this rule.

I worry a bit that its getting unwieldy, so feel free to suggest options to clean up the language a bit.

---

EDIT AT THE TOP:

Promotional posts require community participation or they will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be used in full without payment, it will be exempt from this rule.

Intended to clarify on "paywall" - it has to be open source and run in full locally, no one-time or subscription-locked payment for features, to qualify. Donations don't count as that doesn't limit use, while something like Kavita (which has non-free features behind a subscription, despite the base being open source) would not have the benefit of exemption. The rule intent hasn't changed here, just the wording on the exemption limitations.

---

I've gotten through (I believe) all the comments in the meta thread. So I want to establish a few things, first being a better definition on spam.

Spam is not "I don't like this and its a paid product" or "I don't like this and they used AI/LLMs".

Spam would generally be considered:

• Mass-posting - Posting the exact same post across a bunch of of different communities, rapidly.
• Repetitive Content (aka karma farming) - repeatedly submitting old popular content. I'll note that this is completely irrelevant on lemmy, this was more of a reddit issue due to karma.
• Bot Activity / AI Abuse - Using scripts/bots/gen AI to automate posts and comments.
• Unsolicited DMs - Mass private messages or chats to users, completely unsolicited

I'd say anything other than that deserves a followup rule, and this definition should go in the sidebar.

Regarding the promotional posts themselves, I think something like the 10% rule makes sense - no more than 10% of the account should be self-promotional material or comments within the community.

I do think it makes sense to include an exception for 100% free/libre open source projects. Partially open projects with a closed (paid) component should be subject to the 10% rule. So what I propose as the rule would be:

Promotional posts require community participation or they will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & without any paywalls, it will be exempt from this rule.

Questions, comments, clarifications, and harsh criticisms are welcomed in the comments. As a reminder from my intro post, and because of some comments in the other thread, I will mention:

There are people on both sides of the keyboards, so please be respectful of others.

Edit at the top: My lemmy.world alt has been added as a mod, so now I'm going back through reports (mostly from before I was a mod, so bear with me). You can, of course, send me a dm for anything requiring immediate attention, but I'm also able to see reports properly now.

---

Well its only been a couple days, but the response has been very consistent and functionally unanimous.

Rule 3 is now revised to read:

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

There may be some slight tweaks, but I'm going to consider this good for now.

~~As an important note, I'm still waiting on a ticket response from the lemmy.world team to get my lemmy.world alt added for report purposes. If you see something that requires more immediate attention please send me a message in addition to a report.~~ Also, some of the other rules have been trimmed to just the point of the rule, removing the commentary in them.

In addition, rule 7 (low effort posts) is deleted as everyone seems to agree its handled just fine with votes.

A few related items out of the discussion:

• Posts that are better off in a different community (not just intent, but also a community thats appropriately supported by activity) will be locked only after that community is noted. There is a bit of subjectivity here obviously, so lets play it by ear at the moment. They will not be deleted though, only locked.
• If there is an influx of simple posts about hardware, pictures of setups, etc., then we can go ahead with a weekly sticky for that content. There aren't enough in the log to justify this yet.
• Low effort content is currently well managed with upvotes and downvotes. Again, if there is an influx of low effort content, we can use a different approach.
• Repeated common questions, once enough of them are being seen, will go to an FAQ post or a wiki. Not enough of those in the modlog either right now to justify the effort, but if someone does want to go ahead and make one, we can get that going anyway.

I appreciate everyone's input on this! And remember I'm just here to help, so if there are any other rules / descriptions / whatever you feel should be up for discussion, you can feel free to start a discussion about it.

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:

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.

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.

@hybridsarcasm@lemmy.world has not replied to me (or anyone according to his profile) after that last bit about making me and @ayyy@sh.itjust.works mods, so I'm going to go ahead and work on holding down the fort. Its a bit of a hectic weekend for me with activities for my kids, so you may see some post activity being restored or other such things in no particular order.

So who am I?

Well, I'm a specialist consultant by day, and an avid self-hoster. Off the top of my head, I host:

• Jellyfin
• An over-complicated *arr stack to suit my particular tastes of media management
• Prometheus+Loki+Grafana for my monitoring stack
• Home Assistant
• Personal website
• Immich
• MagicMirror
• ROMM for that fun emulation on the go
• Kavita (mostly because I keep forgetting to change the url on my wife's phone for the other OPDS server) & Calibre (the other OPDS)
• Local AI models for testing purposes mostly
• Endurain for my post-Strava life
• Various stuff for utility for SSO, LDAP, databases, MQTT, so on and so forth

Predominantly running on Proxmox as LXCs, with some docker here and there. So pretty much the same as a lot of you, just another *selfhoster (edit: WHOOPS! I a whole word there, now fixed)

Moderation Style

Lets call it "light touch". I'm pretty sure everyone here is more than capable of handling most things with the appropriate votes - we've seen this with the recent thread that resulted in this moderation change. In case you couldn't also guess from my home instance, I'm a firm believer in people being able to regulate themselves, so as far as I'm concerned that means the rules themselves can be up for discussion as well. As this community is on lemmy.world, of course that means the TOS here must be respected.

There are people on both sides of the keyboards, so please be respectful of others.

The one thing that I just do not tolerate is bigotry.

And finally, feel free to send me a message to address any issues! So lets have some fun with self-hosting.

Edit: Added a direct link to the Lemmy.world TOS for clarity. This community is on Lemmy.world and subject to its terms, as managed by the admin team.