other accounts:
Hello,
we can mark your community as locally hidden, which will prevent non-subscribed users from seeing it. This is however only a local thing and will not affect users on other instances. It will therefore also prevent discovery, as it’s not only removing posts from a feed, but also removing the entire community from being seen anywhere unless accessed directly.
This doesn’t really solve the problem. This person used to scramble/delete their own content in the past before they went to delete the entire accounts.
They’re a rather persistent ban evader who can’t accept not being welcome in some spaces on the internet. Even before they started deleting accounts they already used multiple accounts to evade bans.
I’d be happy to hear suggestions for addressing this without essentially banning all new accounts. Preventing new accounts from participating will only result in them aging accounts for a bit before usage and discouraging legitimate new users from participating.
Hi,
this community is primarily intended for support topics related to this instance, not about general Lemmy topics.
I’d recommend a more general Lemmy/Lemmy moderation community instead, such as one of these (some of them seem to be dead, but a crosspost probably wouldn’t be an issue):
reset federation failures for both dubvee.org and piefed.social, it’s sending again. thanks for the report.
unfortunately i don’t see anything useful in the lemmy logs that would indicate why this has happened.
can you please share the ray id shown by cloudflare? alternatively please send me your ip in a pm.
jordan is also saying that “from the river to the sea” is a call for genocide? if so, please provide a reference
thanks for flagging this, we’ll have to do some research on this phrase. I don’t know the exact details of its usage yet.
how long users should expect
i expect that we get the consequences sorted out before the end of this week.
there’s another high level lw person here acting similarly to the mod in question
would you mind adding some context to this?
Jordan no longer has any responsibilities or privileges beyond being a community moderator at this time.
The original description of our community teams can be found here, but over time this has changed a bit. We’re looking to have this more clearly defined again and are talking to the two active members of the team to figure out a good way forward. Currently, this includes for example reviewing communities with unresolved reports that keep piling up, trying to find new moderators for those communities, and it can also include helping out with instance bans to provide more coverage throughout the day when trolls or spammers show up.
As far as transparency is concerned, there’s still a lot of room for improvement, especially on the timing aspect. We’ve also had more reports in the past about Jordan, but they were either resulting in internal conversations or not necessarily enough to take further actions.
that community primarily is people reporting on behavior of moderators that they disagree with
it’s a range of private and public reports, some of the public ones can be found in !yepowertrippinbastards@lemmy.dbzer0.com.
we’re still working on this, you can find our update here: https://lemmy.world/post/36621226
i don’t think so, but this is part of the lemmy source code, not configurable. i might take a look at changing that for LW though.
hi, this should be fixed now. see also https://lemmy.world/post/36187021 for some additional context.
I believe this should be fixed now.
the issue lies with cloudflare and not lemmy. wold, correct?
the issue seems to stem from a change done by Cloudflare not too long ago, but that doesn’t mean that we’re unable to work around it. i’m currently implementing some changes that should help with this.
any info or links about this cloudfare issue known atm?
the link was included in my previous comment
please translate this into user experience
for the most part, any “read” operations (looking at a post, comment, user, etc) should not be affected by this. for any “write” operations (login, posting, commenting, editing posts/comments, etc.) there seems to be a higher error rate currently related to this. in those cases the action would simply not be completed, and depending on the client (app, default web interface, alt ui) this could range from and endless loading indicator to an error being displayed to nothing being displayed.
if this has resulted into more strict automod functions
no, and this was not an automod removal. you can see the reason why it was removed in the modlog: https://lemmy.world/modlog?postId=36129581
you should also have received a message from our automod informing you about the removal, but automod is only informing you about what happened, not the one taking action in this case.
seems like we’re not the only ones trouble by some changes clouflare did to their OWASP ruleset: https://community.cloudflare.com/t/owasp-ruleset-unexpectedly-has-a-high-false-positive-rate/814544/19
this is a change cloudflare did to the detections they have for http requests to our server. this could affect any API calls from any clients towards our API backend, including automod actions. at most however this would prevent some automod actions from being executed, it couldn’t cause e.g. false positives.
thanks for sharing this.
it seems that cloudflare’s managed rules for the OWASP are hitting a bit much lately. this request has been blocked as “Inbound Anomaly Score Exceeded” with an “OWASP score” of 49, hitting a bunch of rules in the managed OWASP ruleset, many of them relating to SQL injections. i’m gonna have a look at what we can do to tune this down.
thanks for the reminder, it’s updated now