Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pop-up warning people that blocking is public information #5812

Open
Paarsec opened this issue Oct 17, 2024 · 4 comments · May be fixed by #7441
Open

Pop-up warning people that blocking is public information #5812

Paarsec opened this issue Oct 17, 2024 · 4 comments · May be fixed by #7441
Labels
feature-request A request for a new feature

Comments

@Paarsec
Copy link

Paarsec commented Oct 17, 2024

Describe the Feature

I think people should get a popup when blocking someone for the first time, telling them that blocklists are accessible by others.

I also think this fact should be a permanent addition in the little blurb on top of your blocklist for good measure. I believe this will avoid a lot of headaches in the future and increase people's safety.

I can't remember if the popup is already a thing as I've joined way too long ago, but in case it is, I think the text blurb above the user's blocklist would still be a wise addition. Thanks!

Attachments

No response

Describe Alternatives

No response

Additional Context

No response

@Paarsec Paarsec added the feature-request A request for a new feature label Oct 17, 2024
@surfdude29
Copy link
Contributor

I agree that this could be improved. What do you think of the wording I proposed in #3699?

"Blocking is public. Blocked accounts will be prevented from seeing your content and they cannot reply in your threads, mention you, or otherwise interact with you. You will not see their content."

@Paarsec
Copy link
Author

Paarsec commented Oct 17, 2024

I agree that this could be improved. What do you think of the wording I proposed in #3699?

I think the string "Blocking is public" as the first one works perfectly, well done. I hope it gets approved.

@ConnorKrammer
Copy link

ConnorKrammer commented Oct 18, 2024

@surfdude29 Putting my copyeditor hat on for a second—I actually think "Blocking is public" is not clear in the way we want it to be. I think there are basically two core problems:

  • First, blocking is always public, insofar as it's an act that occurs in a public space, and other people can infer that it has happened by observing interactions or seeing involved parties post about it. You can't expect that nobody will ever know you have blocked someone. In this sense, the sentence doesn't update the user's mental model meaningfully.
  • Second, and contra to the former point, blocking is not public at the level Bluesky users will be thinking about. A block on Bluesky is public at the level of technical implementation, and it's important that people know that in theory that data is accessible. But it's not actually public in terms of the site interface, which is how they actually experience "public" and "private" on the site. Saying that blocking is public but without updating their mental models as to what exactly this means risks confusion and anxiety that may actually cause people not to use the feature. Perhaps what this suggests to a user is that clicking the button will post an alert to everyone that they have done so.

I'm not sure you can actually fit into a few words what we want to express here. The idea does not have a shape that fits preexisting mental models closely enough that we can convey it both cleanly and in a highly compressed manner. The closest I personally can manage at the moment might be something like this:

Blocked accounts will be prevented from seeing your content and they cannot reply in your threads, mention you, or otherwise interact with you. You will not see their content.
(i) Block lists are public information. Bluesky does not provide a way for others to view who you have blocked on the site, but 3rd-party services may do so.

This wording could probably be iterated on further. I think "Block lists are public information" is not as precise as I would like, for example. Do consider the structure I used, though: instead of tacking on the bit about public state to a message which is otherwise somewhat orthogonal, give the warning its own space and let it look like a warning or information box, one that augments the context and the message prior to it.

It would also be ideal to provide a link that points to some canonical resource that explains what it means in greater detail, but I do not know if one exists.

Hope I conveyed what I wanted to clearly enough! Thanks for the hard work helping to improve the site for everyone.

@surfdude29
Copy link
Contributor

@ConnorKrammer Thank you for your thoughtful and considered feedback and your suggested wording, and I apologise for only replying many months later.

I have just opened a new PR taking into account your suggestions (with a few changes):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A request for a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants