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.

Sign up for GitHub

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

Jump to bottom

Consider renaming 'ignore' to 'block' #301

Open
turt2live opened this issue Nov 2, 2021 · 1 comment
Open

Consider renaming 'ignore' to 'block' #301

turt2live opened this issue Nov 2, 2021 · 1 comment
Labels
A-Moderation O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement X-Needs-Product More input needed from the Product team

Comments

@turt2live
Copy link
Member

It's a common question that we get for how to block people, indicating that the terminology we use isn't lining up
@SimonBrandner SimonBrandner added O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement X-Needs-Design A-Moderation labels Nov 2, 2021
@germain-gg germain-gg added X-Needs-Product More input needed from the Product team and removed X-Needs-Design labels Nov 2, 2021
@jakewb-b
Copy link

I take the point that people are looking for the block button. However, I'd be concerned that if we change this to 'block' it doesn't reflect what the effect is quite as accurately, which could create more confusion the other way.

If I understand rightly, 'ignoring' someone means I don't see any of their messages in a DM or any room we share, but they're not prevented from sending them, and in fact if I un-ignore them, all their messages become visible again.

So, they're not prevented from sending messages, and they're not aware of any restriction - I just choose not to see anything they say.
To me, that is more me 'ignoring' the user than 'blocking' them.

turt2live referenced this issue in matrix-org/matrix-react-sdk May 2, 2022
@turt2live
Add an option to ignore (block) a user when reporting their events
7be6f59 
This is primarily useful if the content being reported really doesn't belong on your screen, and the room moderators are slow to react.

Ideally we'd use the word "block" instead of "ignore", but we call it "ignore user" everywhere else. See https://github.com/vector-im/element-web/issues/19590 for further context on the word choice.

This change includes a minor refactor to the styles of labelled toggles (for reusability).
@turt2live turt2live mentioned this issue May 2, 2022
Merged
turt2live referenced this issue in matrix-org/matrix-react-sdk May 18, 2022
@turt2live
Add an option to ignore (block) a user when reporting their events (#…
e87bda9 
…8471)

* Add an option to ignore (block) a user when reporting their events

This is primarily useful if the content being reported really doesn't belong on your screen, and the room moderators are slow to react.

Ideally we'd use the word "block" instead of "ignore", but we call it "ignore user" everywhere else. See https://github.com/vector-im/element-web/issues/19590 for further context on the word choice.

This change includes a minor refactor to the styles of labelled toggles (for reusability).

* Appease the linter

* Use a checkbox instead of toggle in the dialog

* Update classnames handling for toggle switch

* Appease the linter
@t3chguy t3chguy transferred this issue from element-hq/element-web May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Moderation O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement X-Needs-Product More input needed from the Product team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@germain-gg @turt2live @SimonBrandner @jakewb-b