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 option to disable CWs #642

Closed
1 task done
TheInitializer opened this issue May 9, 2018 · 6 comments · Fixed by #1422
Closed
1 task done

Add option to disable CWs #642

TheInitializer opened this issue May 9, 2018 · 6 comments · Fixed by #1422
Milestone

Comments

@TheInitializer
Copy link

TheInitializer commented May 9, 2018

This is an option i'm missing on every Mastodon client. I would implement it myself but I have a ton going on in terms of school right now.


  • Tusky Version: 1.7.0

  • Android Version: 8.1.0

  • Android Device: Nexus 4

  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.

@charlag
Copy link
Collaborator

charlag commented May 9, 2018

Hi! Yeah, I know some people (mostly from Pleroma) don't want posts to be collapsed. I think it's a viable option.
Please tell us if you will start working on this and thanks for filling this in.

@adamemerson
Copy link

If you do add this option, please also make it turn off long toot collapsing.

(Or at least provide an option to turn off long-toot collapsing.)

@charlag
Copy link
Collaborator

charlag commented Jan 22, 2019

Mastodon has on option "Always expand toots marked with content warnings" but it's not exposed through the API (so it's probably local). I think it's a good argument in favor of adding such a thing.

@connyduck
Copy link
Collaborator

There is a pull request to expose the setting via the api mastodon/mastodon#9821

@digitalcircuit
Copy link

digitalcircuit commented May 10, 2019

Worthwhile noting that the preferences API has been merged, and Tusky would need to load/store the reading:expand:spoilers boolean via api/v1/preferences.

Looking through MastodonApi.java, it seems like Tusky still uses the previous way of accessing default sensitivity and privacy (api/v1/accounts/update_credentials). All of those settings could probably be migrated to the new API endpoint, too.

For reference from the merged PR, tootsuite/mastodon#10109:

{
  "posting:default:visibility": "public",
  "posting:default:sensitive": false,
  "posting:default:language": null,
  "reading:expand:media": "default",
  "reading:expand:spoilers": false
}

@connyduck
Copy link
Collaborator

https://mastodon.social/@Tusky/102492376435005711

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

Successfully merging a pull request may close this issue.

5 participants