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

Adding a per user "show sensitive content" option #607

Closed
phikal opened this Issue Apr 26, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@phikal

phikal commented Apr 26, 2018

Extending issue #385, I wanted to suggest an option, to automatically show "hidden content" (see for example this account), but on a per-user basis, since there are certain accounts I know won't disturb me, but use this option on all their posts anyways, and others which most certainly do, which I would very much want to hide.

@charlag

This comment has been minimized.

Collaborator

charlag commented Apr 26, 2018

Hi! Thanks for reporting. We should consider that. I think this is a valid use-case but I think it's kinda low-priority (unless someone jumps in with implementation).
Thanks for understanding.

@charlag charlag added the enhancement label Apr 26, 2018

@connyduck

This comment has been minimized.

Member

connyduck commented Apr 26, 2018

Do you mean you want to set the option per each account you are logged in with? We can do that.
Or do you mean you want to have the option for each other user you follow in the fediverse? Because thats definitely out of scope for Tusky. @phikal

@charlag

This comment has been minimized.

Collaborator

charlag commented Apr 26, 2018

I think it's the second and I think it's doable - we just need a set of ids for which we override sensitive

@connyduck connyduck added this to the Tusky 4 milestone Aug 24, 2018

@connyduck connyduck self-assigned this Aug 25, 2018

@mal0ki

This comment has been minimized.

Collaborator

mal0ki commented Aug 28, 2018

Can this be combined with clarifying the language of this setting?

#814

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment