/kbin meta

5 readers

2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

Why doesn't blocking work? (kbin.social)

submitted 1 year ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

I had to block a few users yesterday. Today, I noticed about ten notifications from users I've blocked—they replied to me, continued to make up lies about my heritage, and I continued to see their comments in my notifications.

It seems that the only effect of my blocking them is that I can no longer see their comments in context—although I am still notified of their harassment. This is quite the opposite effect from the one I was going for—I mean, I'm happy to spend less time engaging with them, but the block feature seems to be guaranteeing these bigots the "last word" and preventing me from even reporting them. They can then follow me anywhere on kbin and continue to harass me, the block function is only stopping me from doing anything about it.

At least one of these users is on the same instance as I am, kbin.social.

Why doesn't blocking work?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

Yeah, Mastodon has separate block and mute functions.

Ah, good to know. I'll have to look into it a bit more, but reading https://docs.joinmastodon.org/user/moderating/#block

If you and the blocked user are on the same server, the blocked user will not be able to view your posts on your profile while logged in.

It looks like the limitation that Pamasich and I sort of expected is there. Blocks are basically only possible at your own instance. If the user is on another instance, there's no way to stop them in the fediverse. And that includes it going out to all other instances they federate with too.

I sort of just experienced how this would work if implemented, in a way. A kbin social user posted to a beehaw org magazine. I replied to it, but my post does not seem to have made it to kbin social. However, it's on my instance, beehaw's, lemmy one, etc, because my instance federates with all of those instances. That's sort of what blocking would be like if the original page refused an incoming comment due to a block, all other instances would still accept it. It's possible there's something I'm missing as I'm not super knowledgable on activity pub or the fediverse, so I'll try to learn more about it

[–] [email protected] 1 points 1 year ago

ah, that sucks. feels like it shouldn't be too hard to honor blocks across instances, but idk.

and, yeah, theres' something super janky about the way kbin handles federation...