I’m on another instance where there’s a local user who posted a ton of spammy content before deleting their account. I wanted to block them to filter out their posts, but that appears to only be possible from a different instance that doesn’t know that their account has been deleted. On the other instance, I can’t manually add their account because it doesn’t exist.
Is there an API or something that I can access (say with curl
by hitting an endpoint to force an update to the block list) or any other way of blocking their content? It feels a bit broken / unbaked for the platform not to have a way of blocking content from a user just because they deleted their account.
I’m posting this on two instances because I know some defed from others; I’m hoping that gets this question to someone who knows the answer.
The [email protected] suggestion isn’t that helpful here because that’s intended for .world only, but you could try [email protected], [email protected] (if you’re federated), or maybe the lemmy GitHub?
Apologies, I’ll seek out better avenues.
No worries, easy mistake to make just based on naming. Hope you find an answer!