Hello, beep has been issued a warning to abide by the posting limits in the community while this rule is in place. We're also looking into whether a new community moderator will be appointed.
since this post wasn't to a LW community the removal didn't federate. to see the full picture of our automod actions you have to look at the modlog at the source instance.
the post you created that was removed here was linking to a domain that has been massively spammed by bots in the past, which is why it's in our automod blacklist.
as others already pointed out, you've been unbanned already when we saw the automod notification. you can also find contact in our instance sidebar:
i don't have any evidence whether this domain has been spammed on behalf of the website owners, or whether this was a third party trying to frame them, but since there were no or almost no legitimate links to this domain before the spam bots i'm inclined to believe that this is a very shady website that should be avoided in any case.
all content is generally owned by its creator and only the creator can change it. for lemmy 1.0 this will be changing for marking as nsfw and managing tags, so it seems that this is somewhat being relaxed.
A user‑level version of that, or a proper “deleted” ActivityPub signal, would give people far more control than the current soft‑delete model.
This quite literally already exists.
When you delete posts, comments or PMs, the ActivityPub message is a deletion. How other servers handle this depends on the software, some immediately delete the data, others will retain it for some time and trigger a delayed deletion. Others may not delete it at all. Likewise, if you delete your profile in Lemmy, you have the option to select whether your content should get deleted along with it.
With Lemmy, some of these actions are not always instantly deleting data from the database. For example, if you delete a post or comment, you still have the option to undelete it to restore the original content. From a moderation perspective, it is crucial to not purge everything from the DB without a trace immediately, as this would easily allow abuse by bad actors.
at this point they're long past the point where they'd be tolerated here to keep a single account. they're constantly impersonating and harassing other people, they need the new accounts to be able to evade bans.
feel free to get in touch with us if you have issues with api limits. we can't change them for individual users but we may be able to give you advice on more efficient usage.
your bot shouldn't be logging in every time it checks what is going on; it's best to persist the JWT you get from logging in and keep using it. the signup/login rate limit (which for whatever reason has the same counter) is relatively low to limit abuse, but the other endpoints should be more relaxed. you'd also have to hit pretty high request counts for us to even look at it. i recommend using a separate bot account (see bot rules).
most reports will only be seen by community moderators on our instance. We're typically seeing about 100-200 post/comment reports on any given day, and we don't have the capacity to look at all of them on admin level. If you need to report something to our admin team the best option is to message @lwreport@lemmy.world, which will go straight to our admin team. This does however not make Lemmy's built-in reports useless. Lemmy does not store an edit history for posts and comments currently, but your report stores a snapshot of the contents at that point in time in our DB, which we can look up even if the community moderator resolved the report already.
Hello, beep has been issued a warning to abide by the posting limits in the community while this rule is in place. We're also looking into whether a new community moderator will be appointed.