the latest feature I’ve found is that when an admin deletes your account on their end it produces a ‘not found’ page, overall the software seems much better at filtering out dissent- ironic considering a primary complaint they have is ‘authoritarian developers’ influencing the software in some nebulous way
the way it works on lemmy there’s still some transparency, for example you can still see that the account existed, and has had posts removed by mod so you can figure out the context lemmy has it’s own issues too, like the fact that you can’t see the removed posts; iirc they’re planning to change that.
I don’t have the patience to go through this whole thread, but as for preserving filters on modlog pagination, I just pushed a fix for it. Currently, it would just work on the main branch and hasn’t been backported to the 1.3 branch.
Every single one of their posts says ‘removed by mod’ with nothing in the comment moderation history. As far as I know if they were just banned with the posts manually removed you would still be able to reveal the comment moderation history.
I think the Lemmy user you are referring to above got banned, and their posts got removed as the sub-action, but they did not get purge.
Your account got purged on the Piefed instance you linked above.
Now obviously as you can guess it’s difficult to find an example of a purged account on a Lemmy instance as there’s no filter for that kind of actions in the modlog.
Having a closer look at the modlog for diva’s account on quokk.au, it shows “delete user” and not “ban user”, “delete user” being the Piefed version of Lemmy “purge user”
The modlog leaves a lot to be desired, and piefed mod actions don’t even appear on lemmy instances right now. Mind you, the way Lemmy handles instance bans is also not great either. I have noted this.
As far as I know, if someone from lemmy.world is banned on lemmy.zip (an example) - they are only directly banned from lemmy.zip communities they have commented on. This is why the modlog shows users simultaneously banned from like a dozen comms at once from time-to-time - they’ve just been banned from an instance
But any communities on lemmy.zip that the user banned from lemmy.zip hasn’t commented on, they can still post there. It just doesn’t federate out.
That means a user from lemmy.world could be a nuisance on a lemmy.zip community without the local lemmy.zip mods noticing. This absolutely happens on piefed bans of lemmy users now, and I assume the same in reverse. I saw a user banned from piefed.social still posting on my television@piefed.social community from lemmy.world, but it just doesn’t federate out.
That is correct, and this happens to be another one of the issues which is already fixed for version 1.0. Basically for each ban we also store which instance it’s associated with, which is shown in the modlog and the new mod action notifications. If you’re interested I can link you the PR.
the latest feature I’ve found is that when an admin deletes your account on their end it produces a ‘not found’ page, overall the software seems much better at filtering out dissent- ironic considering a primary complaint they have is ‘authoritarian developers’ influencing the software in some nebulous way
I’m quite sure it’s similar on Lemmy: if an admin purges a user, their profile won’t be accessible anymore
the way it works on lemmy there’s still some transparency, for example you can still see that the account existed, and has had posts removed by mod so you can figure out the context lemmy has it’s own issues too, like the fact that you can’t see the removed posts; iirc they’re planning to change that.
in fact on piefed, if you wanted to review the modlog to see who has been getting account deleted, it doesn’t let you see beyond page 1
the next button resets the search
Was that account purged or banned? IIRC there’s a difference, and purged accounts would show ab empty profile without any posts
Good point about the modlog page 2, @rimu@piefed.social or @wjs018@piefed.social can this be fixed quickly? If not I’ll make a Codeberg issue
I don’t have the patience to go through this whole thread, but as for preserving filters on modlog pagination, I just pushed a fix for it. Currently, it would just work on the main branch and hasn’t been backported to the 1.3 branch.
Great, thank you !
@diva@lemmy.ml FYI
Every single one of their posts says ‘removed by mod’ with nothing in the comment moderation history. As far as I know if they were just banned with the posts manually removed you would still be able to reveal the comment moderation history.
There are two different actions
The documentation explains the difference
https://join-lemmy.org/docs/users/04-moderation.html?highlight=purge#how-to-moderate
I think the Lemmy user you are referring to above got banned, and their posts got removed as the sub-action, but they did not get purge.
Your account got purged on the Piefed instance you linked above.
Now obviously as you can guess it’s difficult to find an example of a purged account on a Lemmy instance as there’s no filter for that kind of actions in the modlog.
TIL, I’m not an admin so I never interacted with that functionality (nor did I rtfm, clearly)
already planning on making a sequel yptb post complaining about being purged
Feel free , at least maybe some other admins can confirm the difference between ban and purge on both platforms 😅
The API has a filter for AdminPurgedPerson, but the result doesn’t include any info on the purged user.
Indeed.
Having a closer look at the modlog for diva’s account on quokk.au, it shows “delete user” and not “ban user”, “delete user” being the Piefed version of Lemmy “purge user”
https://quokk.au/modlog?mod_action=&suspect_user_name=diva%40lemmy.ml&communities=&submit=Search
For me, when I clicked “next” it instead just changed from local -> to all. This seems more like a bug rather than anything deliberate.
looks like a broken ui, I can manually input the page number to navigate it, but what a pain in the ass to use, wasn’t saying it was deliberate.
The modlog leaves a lot to be desired, and piefed mod actions don’t even appear on lemmy instances right now. Mind you, the way Lemmy handles instance bans is also not great either. I have noted this.
What’s wrong with instance bans on Lemmy?
As far as I know, if someone from lemmy.world is banned on lemmy.zip (an example) - they are only directly banned from lemmy.zip communities they have commented on. This is why the modlog shows users simultaneously banned from like a dozen comms at once from time-to-time - they’ve just been banned from an instance
But any communities on lemmy.zip that the user banned from lemmy.zip hasn’t commented on, they can still post there. It just doesn’t federate out.
That means a user from lemmy.world could be a nuisance on a lemmy.zip community without the local lemmy.zip mods noticing. This absolutely happens on piefed bans of lemmy users now, and I assume the same in reverse. I saw a user banned from piefed.social still posting on my television@piefed.social community from lemmy.world, but it just doesn’t federate out.
That is correct, and this happens to be another one of the issues which is already fixed for version 1.0. Basically for each ban we also store which instance it’s associated with, which is shown in the modlog and the new mod action notifications. If you’re interested I can link you the PR.