I think I volunteered to help moderate it about 3 months ago 😕

Using this approach, I am seeing none of those posts on /science. I updated the filters a bit today. The top post is a legitimate article from 2024-04-13 and is by HeartyBeast.

Now, I understand that this is seen as an unnecessary step (too fancy) for some. People want zero ads out of the box without anything extra. So I’m thinking about the next approach here.

Framing the problem:

• Filtering should be automatic
• End-user wants zero additional setup
• There is no active upstream development
• It’s not possible to inherit moderation of a magazine due to some queue of moderator application requests that is not being approved

The third point and fourth points are important here, since that’s currently intractable. You can’t reconcile zero additional setup with that.

But let’s suppose becoming moderator of a defunct magazine (point 4) were possible while point 3 remained unresolved. In other words, at least moderators can try to pick up the pieces. Something being underestimated here is how annoying it would be for the moderator to manually cull posts every single day. I think you would have instant turnover after a couple of weeks once the tedium sets in. Manual solution is not good. Clearly, automation is needed on the moderation side.

So assuming you could actually inherit a magazine, but with no guarantee of upstream development, what about restructuring the tool above so that it’s for moderators, instead of end-users? That’s pretty easy, and I could make it something the moderator clicks once and it’s done, auto-banning the posts. This is a pretty good method.

But you can’t inherit moderation right now, so that’s back to square one.

Realistically, that leaves these options at the moment:

• Wait (a long time) and see
• Use the tool above and make magazines readable, albeit at some sacrifice of convenience (?)
• Migrate to another instance

Third approach is the path of least resistance and is best for most casual users. Second is for diehards who cannot move instances due to some personal or technical reason. First approach is the most annoying and eventually leads to the third approach after frustration sets in.

Pick your poison, I guess. I can’t think of any other prophylactic approach at the moment, maybe this comment triggers some idea.

I think I’m going to give up on Kbin. Every time in enter it’s full of spam, so is not worth posting anything since is going to be buried in spam anyways

Real posts (from kbin.social magazines) are becoming quite rare. I find myself coming to this site now to do the following circuit:

1. sort by new and report SPAM and block users
2. scroll through headlines and read (the few) recent comments/posts to mags I’m interested in
3. come to kbinMeta and see if anyone else is seeing what I’m seeing and feeling the same way
4. see if the radio silence has yet been broken by the dev

It’s a fascinating case study in the rise and fall of an internet community and digital communication platform. And it highlights one important fact about human community management and technology development: COMMUNICATION IS KEY.

Yeah, I can’t find it in abandoned mags, else I would have just taken it and cleaned it up.