/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

Is Blocking Ever Going To Block? (kbin.social)

submitted 1 year ago by FfaerieOxide@kbin.social to c/kbinMeta@kbin.social

72 comments fedilink hide all child comments

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.

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

[–] Sethayy@sh.itjust.works 0 points 1 year ago (1 children)

This blocked=true would then require the server to have a massive if statement, that can't be (usefully) cahched cause its user and post specifc. Extra branching in the code is gonna have a less pretty output as is, but times that by both the number of users and number of posts that the entire instance is federated with?

Just gonna make the fediverse even less popular with higher server costs, and will for sure be abused by the DDoS'ers that are already plaugeing popular instances. All this would them be negated from the 2 seconds it takes on any lemmy app I've used, where you can just press browse as guest.

[–] FfaerieOxide@kbin.social 1 points 1 year ago

Can't reply as a guest though, can you?