@Gordon_Freeman
It really depends on the very magazine. Basically, it’s magazines with Ernest as sole moderator where these problems occur. I’d give it a wait.
@Haus

@bayaz Thank you! This is even worse than I thought! I will try some things out in the near future in order to find a stable way for banning accs.

@bayaz It’s you who gave me food for thought, alongside many other moderators! I only found out yesterday how to properly ban spam accs on kbin.social.

I really appreciate all efforts to grow and take care of communities, be it on kbin, on lemmy, or on mbin! Every day, I try to keep learning from other moderators.

Given the sheer lack of moderation tools, many mods do great work. I hope the situation will improve so that moderatoring will become easier.

@Kierunkowy74
Yes, moderators can access the reports tab within the magazine panel. Every report must include some reason, hence moderators see them. Regarding bans: without giving a proper reason, no ban can come into effect.

You can also check the modlogs on kbin and lemmy instances for bans (does not apply to mbin).
@bayaz @jayrhacker

@jayrhacker
Would you elaborate on this?

The instance has clearly communicated that it primarily serves as a test instance, i.e. it does not strive for or want to guarantee stability.

that’s just not true > when c.s switched over to dev branch in april 2023, this was not motivated by wanting to become a “test instance” > rather, this was a desperate move to keep the instance afloat which by then had been become quite wonky > afterwards, things got even worse, so the transpicuous idea to rebrand the whole project

noting, absolutely nothing about f.s is about being a test instance > see also atomicpoet’s post about movin away from f.s - f.s was supposed to be a flagship instance, but only evolved into a shipwreck

the biggest disadvantage of firefish: its community which has become like a sect - but that had been going on for a very long time already …

even weirder if it’s a Mastodon fork such as Glitch-soc, Hometown, Fedibird,… since they use older Mastodon versions as base

i myself have been active on calckey/firefish, hajkey and iceshrimp instances, and never had a problem interacting with people on mastodon forks > there had been some backfilling issues, but they got solved > but federation problems do exist: so far, it is not possible for *key users to interact with lemmy instances; also link posts from kbin do not show up on *key timelines

since you are on a lemmy instance: be aware that people on the *keys cannot interact with lemmy instances

firefish is rebranded calckey, a misskey fork > project has been in trouble since, hmmm, may 2023 > the *keys offer a very different interface, emoji reactions and lots of other features which mastodon does not have > *keys ui is pretty nice compared to mastodon - in the end, this is a matter of taste > but other than that, particularly firefish and its forks do not scale well: there is a reason why former firefish.social admin atomicpoet chose to migrate to another instance, though atomicpoet’s post tries to hide the reasons for moving > note: firefish.social is a special case - this instance is a lost cause with outages beyond comparison > instead of building up a community at firefish.social, the admins effectively destroyed the community by introducing new experimental features instead of focusing on stability