I saw that in the hexbear modlog and was wondering what happened too.
It looks like someone (Alaskaball apparently) was doing some house cleaning because a bunch of older posts and comments were recently removed. One of them included one of your posts from a month ago: https://hexbear.net/post/7232184 which had a variation on a misogynistic slur in the title. That would be my guess as to the reasoning, anyway. And Alaskaball has been around as a hexbear mod for a very long time, I think since the founding and later became an admin.
Also I’m just curious about the screenshot you posted. Is that a view of something only mods can see? Because as far as I knew, it wasn’t possible to see which mod performed which action.
Are you using an app? Is the screenshot from a moderator-only view of the modlog? Because yeah, as regular users, not moderators, using the website, we can see the actions in the modlog, but we can’t see what mod performed them. In fact I remember that being an issue of contention on hexbear, some people wanting to be able to see which mod did what, but the response was that it would create too much drama if users got to see which mod removed their comments or banned them.
Which? How? And in this case, Saymaz was using Summit, which I checked and Summit does not show mod names for mod actions (unless the user is an admin or a moderator of that specific comm the action happened on).
So if someone has an account from a Kbin instance that is federated with a Lemmy instance, they can see stuff that normal Lemmy users can’t? Do you know if it requires them being an admin of a Kbin instance or just normal user?
Oh, I bet you have an app client for it that is able to show that info, different than default. That might explain it. It’s probably info that is not really “private” but doesn’t get displayed in default interface.
I just downloaded the app Saymaz uses, Summit, but I still can’t see mod names with it. I’m almost positive it’s because Saymaz is a moderator too, which gives them privileges that non-mod users don’t have.
Strange. I wouldn’t think being a mod in one “community” would give that kind of access, since anyone can make one, right? But I don’t know enough about how lemmy works in general, I guess.
I tried looking a little more into it, and so far as I can tell, Saymaz should not be able to see who performed the mod actions. You’re right that them being a mod on lemmygrad should have no impact on their ability to see the mod name for a mod action on hexbear. Only admins and other mods for that comm should be able to see who performed the mod action. But it doesn’t appear to be something having to do with the app Summit either, which does abide by the lemmy protocol for not sharing the names of mods on mod actions. Which is the default setting, though instance admins can choose to share that information if they want, but almost none do, and hexbear certainly doesn’t. So I still really don’t get why Saymaz was able to see that it was Alaskaball. It’s weird.
I saw that in the hexbear modlog and was wondering what happened too.
It looks like someone (Alaskaball apparently) was doing some house cleaning because a bunch of older posts and comments were recently removed. One of them included one of your posts from a month ago: https://hexbear.net/post/7232184 which had a variation on a misogynistic slur in the title. That would be my guess as to the reasoning, anyway. And Alaskaball has been around as a hexbear mod for a very long time, I think since the founding and later became an admin.
Also I’m just curious about the screenshot you posted. Is that a view of something only mods can see? Because as far as I knew, it wasn’t possible to see which mod performed which action.
So I escaped reddit to experience reddit 2.0?
It’s in the lemmygrad modlogs.
I see it in the logs, but like the other user said, I don’t see the mod name in the logs. 🤔
It is showing in my client though
Are you using an app? Is the screenshot from a moderator-only view of the modlog? Because yeah, as regular users, not moderators, using the website, we can see the actions in the modlog, but we can’t see what mod performed them. In fact I remember that being an issue of contention on hexbear, some people wanting to be able to see which mod did what, but the response was that it would create too much drama if users got to see which mod removed their comments or banned them.
I am using summit.
You can see them on some platforms.
Which? How? And in this case, Saymaz was using Summit, which I checked and Summit does not show mod names for mod actions (unless the user is an admin or a moderator of that specific comm the action happened on).
Kbin. They’re pretty open with federation too.
So if someone has an account from a Kbin instance that is federated with a Lemmy instance, they can see stuff that normal Lemmy users can’t? Do you know if it requires them being an admin of a Kbin instance or just normal user?
Oh, I bet you have an app client for it that is able to show that info, different than default. That might explain it. It’s probably info that is not really “private” but doesn’t get displayed in default interface.
I just downloaded the app Saymaz uses, Summit, but I still can’t see mod names with it. I’m almost positive it’s because Saymaz is a moderator too, which gives them privileges that non-mod users don’t have.
Strange. I wouldn’t think being a mod in one “community” would give that kind of access, since anyone can make one, right? But I don’t know enough about how lemmy works in general, I guess.
I tried looking a little more into it, and so far as I can tell, Saymaz should not be able to see who performed the mod actions. You’re right that them being a mod on lemmygrad should have no impact on their ability to see the mod name for a mod action on hexbear. Only admins and other mods for that comm should be able to see who performed the mod action. But it doesn’t appear to be something having to do with the app Summit either, which does abide by the lemmy protocol for not sharing the names of mods on mod actions. Which is the default setting, though instance admins can choose to share that information if they want, but almost none do, and hexbear certainly doesn’t. So I still really don’t get why Saymaz was able to see that it was Alaskaball. It’s weird.
Summit devs, could you just take a look on the issues before the next update?