Which issues are you referring to? Instance shouldn't matter as long as federation works properly, I think the bot has simply crashed and I don't have access to restart the server before next week.
Yes, I've noticed an uptick in connection errors from the lemmy.world servers, which is likely the reason. I am planning on rewriting the bot in Erlang/Elixir from python and will look into the fixing any potential issues once that happens. I don't have access to the server at the moment as I'm away on holiday, so if the bot is down, I can't restart the process unfortunately.
It’s not helping if some bitch on her menstrual cycle comes and spams her keyboard without any valid points
You've already previously been given warning for breaching our Code of Conduct section 3.5 (Hate Speech: Do not make remarks directed at sex, gender...). This is your third strike within 2 months and your account is now at risk of receiving a permanent ban if further breaches are made within 365 days.
Since this is strike 3, your account will be given a 14 days site-wide temporary ban.
If you don't have anything positive or helpful to say, it would be better to just not reply. If you think the post shouldn't be posted here, use the report function instead.
When on communities hosted by programming.dev, please follow our Code of Conduct. Repeated breaches of our CoC will lead to a temporary ban from our instance.
Got it. I saw that Vacant was then in the mod list, I've transferred the community to you (based on seniority) and removed Vacant from the moderator list.
Just a reminder that section "3.6. Vote Manipulation" of programming.dev's CoC prohibits targeted downvotes and mass downvoting of posts. You've already broken it by mass downvoting JokeDeity's old posts, please don't break it further. If you keep breaking our CoC, a temporary ban may be given.
It is a precautionary policy to avoid what is currently just a theoretical. You'll be the first to create personal blog community so it will be interesting to see how it works out.
Nothing is set in stone of course and policies may be revised, I won't make any claim that the current set of guidelines are perfect and immutable.
The intention of requiring a 3rd party to act as a moderator is to avoid mod abuse from the blog author such as deleting comments or banning people for unreasonable reasons. E.g. someone correcting an error in a blog post and then having their comment deleted and banned by the author in retaliation.
Ideally Lemmy would have more granular level of mod authorisation so that we could just remove access to deleting and banning people.
If someone makes a non-relevant post in the community, it would be removed. If it becomes a recurring problem, we can look into automating that process.
The mod tools are unfortunately pretty poor on Lemmy. For adding/removing moderators via the GUI the person must first post/comment in that specific community. You can then via the context menu of that post/comment add someone as a mod.
The alternative is to interact with the Lemmy API directly via a script.
I've added myself as a moderator, although the whole admin team may operate as moderators, similar to !meta@programming.dev.
If you got additional changes you want to make to the community, e.g. add additional rules like make it explicit that only you can post, or add a banner to the community you should do it now before you're removed as a moderator. Otherwise you can always DM me/the admin team if you want to make changes to it.
Edit: As Blaze pointed out, you can use alternate frontends like https://t.programming.dev/ to gain additional GUI mod tools
If you can't see posts you make on hidden communities that you are subscribed to on your profile, that sounds like a possible bug, and I'd encourage you to report the issue to the Lemmy repo
UlrikHD @ UlrikHD @programming.dev Posts 9Comments 204Joined 2 yr. ago
The bot is up and running again