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.

not at all. nobody can revert edits, only the creator can edit it again.

moderators can restore removed (mod action) posts and comments, but not deleted (creator action) posts and comments.

https://semver.org/#spec-item-4

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

that isn't saying that you should change things, but it's technically not against semver.

given that the lemmy api is versioned separately though and it's currently at v3, with v4 in active development, that would be good to avoid breaking changes there. I don't know if that one is supposed to be sever though.

many communities would be happy to have more mods. many of these cases come from the lack of people volunteering to moderate a community. this is already being considered when people are promoted as moderators in communities by our admin or community team if a community doesn't have active moderators. we already try to find people that aren't already moderating as many communities in those cases.

this comment section is not a place to rant about other instances

I don't believe it is.

There weren't any network related changes from 0.19.6 to 0.19.7 and we haven't seen this behavior with any of the 0.19.6 instances yet.

The requests are visible with details (domain, path, headers) in Cloudflare, but they're not showing on our proxy server logs at all.

a moderator on another instance than the community instance

that was a logic flaw for the selection of which reports are considered for alerting. a fix is currently being deployed, but you should be good for the next 2 days anyway.

Hi,

this was unfortunately an error on our end.

Please bear with us while we work on resolving this situation.

so far this has been a single case with kbin.earth and lots and lots of cases with kbin.social.

no other instances have been observed behaving like this yet.

it's mostly !asklemmy@lemmy.ml, !asklemmy@lemmy.world, !opensource@lemmy.ml, and !selfhosted@lemmy.world, though some of the latest spam also started arriving in !warframe@dormi.zone.