9
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jun 2023
9 points (71.4% liked)
Blind Main
473 readers
1 users here now
The main community at rblind.com, for discussion of all things blindness.
You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.
founded 1 year ago
MODERATORS
Because the documentation on how to set up and run a kbin instance is incomplete. Entire sections just say todo. We need something we can run now, not something we might be able to run in October, if we are lucky.
I suppose that makes sense, given the deadlines. I just hope it works out and that the accusations about the arbitrary issue closing and dismissal of problems turns out to be false.
It's never happened to any of the issues I opened. Keep in mind that a lot of issues people have when hosting Lemmy are going to be because they misconfigured the database, or the server OS, or the web server, or one of a thousand other parts that the Lemmy developers can't fix. Our Stability issues were because nginx and docker had some misconfigurations for our traffic levels. Not a Lemmy problem, and the issue about the same problem someone else opened was closed, as it should have been. But at least the install and configuration process was well enough documented that the issue eventually got found and fixed (though not by me).