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

Feature request: allow user to elect equivalent of !blur by default on another user's post #9

Open
davekasten opened this issue Jun 23, 2023 · 1 comment

Comments

@davekasten
Copy link

See discussion here and upthread of it https://bsky.app/profile/pfrazee.com/post/3jyulblltls2x

Proposed feature: Give user Alice a feature to say, "treat all images from user Bob, who indeed I do want to follow, as if they were given !blur".

Rationale: There are many users (I know a bunch of them!) who use Twitter for tracking news on violent groups. The accounts they follow may often, as part of doing their job to report war crimes, post photos of mass atrocities, bombing sites, etc. in addition to other content (e.g., text-only posts summarizing a statement made by a terrorist group). Such violent-news accounts may occasionally forget to set blurs on their own, and labeling services might or might not happen to capture that individual user Bob's content for boring implementation reasons. It would be nice for Alice to be able to avoid traumatizing content by default.

I understand from discussion with @pfrazee in linked thread above that this isn't anticipated as a feature for labels themselves for design clarity reasons, but think this would be useful to have otherwise. It also tracks (if I understand correctly) the fact that !filter or !no-promote is kind of like a mute, so it feels reasonable to give users a feature they can use themselves to mimic the other imperative, too.

Thanks for listening!

@pfrazee
Copy link
Contributor

pfrazee commented Jun 25, 2023

Not a weird request, I think we could look at this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants