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

Add indication that you have been blocked in web UI #10420

Merged
merged 1 commit into from
Mar 29, 2019

Conversation

Gargron
Copy link
Member

@Gargron Gargron commented Mar 29, 2019

No description provided.

@Gargron Gargron added the ui Front-end, design label Mar 29, 2019
@Gargron Gargron merged commit bd02ec6 into master Mar 29, 2019
@ykzts ykzts deleted the feature-show-blocked branch March 29, 2019 23:53
@inmysocks
Copy link

This is just a gigantic gift to harassers at the expense of people being harassed. Who else would this help?

This violates some of the very basic principles for making a system that is in any way robust against harassment. 'Don't feed the trolls' as they say, here by blocking someone you are giving them a clear indication that they have had an effect and you are just encouraging them to find another channel for harassment. You are never supposed to give people who are harassing you any indication that you hear or don't hear them.

@nightpool
Copy link
Member

nightpool commented Mar 31, 2019 via email

@inmysocks
Copy link

That rational is 'it isn't perfect so it is ok to make it worse'. People have been talking about how existing blocks and anti-harassment functionality could be improved. This is going in the opposite direction.

As I said, who does this help other than harassers? It just makes it easier for them to see that they have been blocked specifically instead of the account being made private or deleted.

@bgcarlisle
Copy link

bgcarlisle commented Mar 31, 2019

I am struggling to see who this helps, aside from abusers.

I would really rather not have people dunking on other people by posting screenshots showing that they got blocked as a punch-line to a joke, like they do on Twitter, and this will only enable this really terrible behaviour from Twitter to migrate over.

@narFnarF
Copy link

I am a bit concerned too. I'd like to know what is the reasoning for this change. I see from nightpool's answer that there are some technical concerns too.
I'm wondering if there would be other options.

@nivex
Copy link

nivex commented Mar 31, 2019

blocks have always been visible to the user blocked, since they stop a blocked user from being able to see the other user's posts.

Fine, but did it explicitly say that the user had been blocked? I'll bet not since this PR exists. A cryptic error about not being able to see that profile or post gives plausible deniability as opposed to explicitly stating that a block exists.

If I follow a direct link to a follower-only post, I don't get an indication stating this, I only see an error message stating the post couldn't be found. Blocks should be the same way.

Concur with previous comments about abusers taking advantage of this. Please unmerge.

@joshgiesbrecht
Copy link

Agreeing with the above concerns

@kindfulkirby
Copy link

Wow, this is a terrible idea.
I thought one of the points of mastodon was to leave twitter's anti-features (like this one) behind!

@ealgase
Copy link

ealgase commented Mar 31, 2019

I really like this change. If someone's being harassed and they block the harasser, it acts as a wake up call to the harasser to stop. If they make a new account, they'll get reblocked and banned from that instance pretty quickly.

@Gargron
Copy link
Member Author

Gargron commented Mar 31, 2019

The discussion seems to be happening here: #10433. Let's not split it up.

@SelfsameSynonym

This comment has been minimized.

@Lana-chan

This comment has been minimized.

@mastodon mastodon locked as spam and limited conversation to collaborators Mar 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ui Front-end, design
Projects
None yet
Development

Successfully merging this pull request may close these issues.