Link.wav [he/him]@beehaw.org to Beehaw Support@beehaw.org · edit-21 year agoPermanently deletedmessage-squaremessage-square49fedilinkarrow-up148arrow-down10file-text
arrow-up148arrow-down1message-squarePermanently deletedLink.wav [he/him]@beehaw.org to Beehaw Support@beehaw.org · edit-21 year agomessage-square49fedilinkfile-text
minus-squareLink.wav [he/him]@beehaw.orgOPlinkfedilinkarrow-up11·1 year agoThat’s good, but you should see it from the end of federated instances. I can’t possible explain to you how much spam there is coming from kbin.
minus-squareshagie@programming.devlinkfedilinkarrow-up2·1 year agoYou can see the spam removed via modlog at Beehaw - https://beehaw.org/modlog/22775
minus-squareBuelldozer@lemmy.todaylinkfedilinkarrow-up7·1 year agoKbin doesn’t federate mod actions. That’s the whole problem.
minus-squareshagie@programming.devlinkfedilinkarrow-up4·1 year agoYep. My comment was showing “if you want to read/see that there’s a spam problem despite what one would see as a user on kbin, the mod log on beehaw will show you the removal of spam that made its way to beehaw.”
I’m on kbin and never see spam, ever…
That’s good, but you should see it from the end of federated instances. I can’t possible explain to you how much spam there is coming from kbin.
You can see the spam removed via modlog at Beehaw - https://beehaw.org/modlog/22775
Kbin doesn’t federate mod actions. That’s the whole problem.
Yep. My comment was showing “if you want to read/see that there’s a spam problem despite what one would see as a user on kbin, the mod log on beehaw will show you the removal of spam that made its way to beehaw.”