MrKaplan

As long as you don't use it for ban evasion or e.g. voting on the same content from multiple accounts it's fine.

i don't remember if banning with content removal removes mod status, but when banning with content removal and they're the sole mod their communities will also get removed.

1. the person is not MIA
2. there have not been any post reports in this community recently
3. on a quick glance, the recent posts do not appear to be off topic
4. a fresh account requesting this and apparently misrepresenting the situation does not give you a good look

nice try

I don't think that's possible.

You could submit a feature request here if there isn't one already: https://github.com/Fedihosting-Foundation-Forks/lemmy-ui

it doesn't appear to be about LW.

@op:

you can try to visit the instance domain directly and check the instance sidebar there.

if it's lemmy it will also show the admins in the sidebar, if it's other software it can be harder to find. you can then look up the admin users from LW and send them a pm if they don't have any other contact info on their instance.

your mod status has been restored

I think that is just a limitation in Lemmy UI, not the API

these are not Lemmy.World communities, we can't do anything about those.

they were probably migrated to FediNSFW instead.

there are quite a few ways to use more granular targeting. for example, we have specific url patterns that get challenged if certain headers have certain values and are missing others, while other urls won't get challenged.

it would be trivial for them to not DDoS and yet they keep doing it.

if they were calling Lemmy APIs directly they would significantly reduce the load they bring to our service. if they were speaking ActivityPub they could even get the content delivered to their front door directly via federation.

they don't care that they DDoS websites. they don't care about optimizing for how certain types of websites are built, to reduce impact on third parties. the only language they speak is DDoS.

they intentionally spoof legitimate browser user agents and cycle through massive ranges of IP addresses. they have enormous pools of IPv4 addresses available that allow them to only use each IP for a couple of requests before cycling to the next one, which is yet another way they evade detection, as they are bypassing any rate limits we have configured that way.

we're currently challenging visitors who aren't logged in regardless of the browser due to extremely aggressive LLM scrapers. as long as you're staying logged in you won't get challenged.