this post was submitted on 21 Aug 2023
7 points (100.0% liked)

/kbin meta

2 readers
1 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
 

Currently users you block can still see your posts, reply to those posts, and trigger notifications when they do reply.

You can read the beginning of messages people you have blocked in your notifications tab, but have to unblock users to see the rest of what everyone else reading the replies to your post can see.

A "blocking" feature that is only inconvenient to the blocker is worse than no blocking feature at all, equivalent to trying to escape a fistfight by turning invisible but actually just closing your eyes.

(page 2) 23 comments
sorted by: hot top controversial new old
[–] skullgiver@popplesburger.hilciferous.nl 0 points 1 year ago (1 children)

I see what you want out of the blocking feature, but it can't work reliably with ActivityPub enabled on your account.

The only way to accomplish this, would be for kbin to provide a "don't federate any of my comments or posts" button, or even a personal federation whitelist, which prevents your contributions from reaching other servers where blocking cannot be guaranteed. Only then could Kbin start hiding your posts from certain users. You would also need to hide your comments from logged-out users, of course. This would also come with some database modifications that would be pretty difficult to get right.

Perhaps you could find a few programmers that share your concern and create a fork of the Kbin code, with your own server where you can attempt to apply this blocking mechanism.

Aside from the fact an alt account is pretty easy to register, you just can't implement hiding your posts from other people in a system that federates with Kbin or its alternatives.

load more comments (1 replies)
load more comments
view more: ‹ prev next ›