Skip Navigation

Posts
0
Comments
235
Joined
2 yr. ago

  • could be that it's the same thing, in this case it's the result of a user deleting their account.

  • you seem to be lost.

    this community is about lemmy.world, not a general support community.

  • might still have been related, i guess we'll never know.

    the rule i changed did look like it had some false positives at least, so even if it wasn't that it should fix issues that could have been experienced by others randomly.

  • there is a possibility that this was caused by a cloudflare rule that was not scoped narrowly enough to achieve what it's intended for. does this issue still persist for you?

  • while it would likely be a good idea to limit this, i don't see a limit in the code that would prevent from blocking more users. what's the actual error message you're seeing?

  • Sure, the same applies to any other lemmy-internal contact method though such as posting to !support@lemmy.world or sending a pm to @lwreport@lemmy.world.

    Our automod doesn't currently inform people that they're banned or how they'd appeal that though. We usually review automod actions within an hour though, in most cases false positives are sorted out before the user even notices them.

  • you can't use lemmy PMs while you're banned from the instance.

    appeals can generally be made in any way that will reach our team; email addresses are listed in the instance sidebar and community sidebar at https://lemmy.world/c/support.

  • the domain you posted a link to was in our automod blacklist due to previously being used by spam bots.

    upon review it appears that this domain serves user generated content by different users that can be determined in the URL path. in those cases we typically only ban those users rather than the entire site if it's not overly spammy.

    we also usually review automod actions quickly, although in this specific case we must have missed this, as we had a lot of other true spam removals in the last days.

    you have been unbanned from LW and your post has been restored.

  • we'll try to get the post out the coming week, at this time we're roughly looking at updating late January.

  • please at least try to make an effort to understand technology.

    after we received the email about account recovery from the email address linked to Don_Dickle we sent instructions there for how to regain access to that account.

  • Us not upgrading has nothing to do with making a point.

    We're aiming to run a stable instance, which can come at the cost of delayed updates.

    We didn't update to 0.19.4, and a few weeks later 0.19.5 was released with a number of critical bugfixes.

    0.19.6 will have several more fixes for issues introduced in 0.19.4+, such as a fix for remote moderators updating local communities, allowing admins to filter modlog entries by moderator, as well as some performance issues reported by other instances.

    We usually wait for other instances to run the latest version for some time to allow bug reports to surface before we update ourselves.

  • we've switched from using multiple federation sending containers (which are supposed to split receiving instances across workers) to just using a single one.