I changed the password after leaking that screenshot
presumably in the time between leaking and changing it? once the password is changed the old password won't work anymore, and neither will any of the previous login tokens.
Lemmy has a feature for taglines where you'll see a random one on every refresh. We used to have a selection of a few communities in there, but at this time we don't have anyone available who has spare time to maintain this. We're open to suggestions or even someone joining e.g. our matrix and we'll be happy to set up a group chat for collecting communities and adding/rotating them in our list.
This is instance specific, so each instance has to maintain this on their end.
we can mark your community as locally hidden, which will prevent non-subscribed users from seeing it. This is however only a local thing and will not affect users on other instances. It will therefore also prevent discovery, as it's not only removing posts from a feed, but also removing the entire community from being seen anywhere unless accessed directly.
This doesn't really solve the problem. This person used to scramble/delete their own content in the past before they went to delete the entire accounts.
They're a rather persistent ban evader who can't accept not being welcome in some spaces on the internet. Even before they started deleting accounts they already used multiple accounts to evade bans.
I'd be happy to hear suggestions for addressing this without essentially banning all new accounts. Preventing new accounts from participating will only result in them aging accounts for a bit before usage and discouraging legitimate new users from participating.
this community is primarily intended for support topics related to this instance, not about general Lemmy topics.
I'd recommend a more general Lemmy/Lemmy moderation community instead, such as one of these (some of them seem to be dead, but a crosspost probably wouldn't be an issue):
i tend to be too optimistic on the timelines in which we get things done, especially when they are moderation related. we have just published an official update on the current situation: https://lemmy.world/post/36621226
should we just purge all mods of LW communities because someone says so? we don't arbitrarily remove mods without a proper review. it's not the action of removing someone that requires time but the review whether it should be done.
jordan has been removed from our community team several days ago and we're still reviewing further stuff to determine additional actions to take.
there is no clear date to put on this other than my previous comment about it taking several days, as this is all shitty work that takes time and is not something that anyone is looking forward to do. it's obviously our responsibility to review an act in situations like this, but there is only so much time available from volunteers. i'm hoping that we can finalize it this weekend, as weekends tend to be when people have more time available.
there have been multiple voices within our team, as well as from Ruud, to simply strip his moderator permissions from all communities, but this is not something aligning with our rules, especially as this specific part was established after the c/vegan drama some time ago. there are multiple reasons justifying removal of moderators from LW communities, but if we apply them we need to ensure that we have proper justification for that, for every affected community, which is the main thing that is currently still being worked on. i expect that we will find valid justifications for at least some communities, but we need to do this before the removal.
the actions taken so far were primarily relating to his behavior while being a member of our team, not due to his behavior as a community moderator or regular user, as we intend to hold our team to higher standards than regular users or moderators, making this a lot easier to justify.
presumably in the time between leaking and changing it? once the password is changed the old password won't work anymore, and neither will any of the previous login tokens.