Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Enable CWs for given tags when tooting #9

Closed
1 of 4 tasks
hughrun opened this issue Aug 21, 2019 · 1 comment · Fixed by #61
Closed
1 of 4 tasks

Enable CWs for given tags when tooting #9

hughrun opened this issue Aug 21, 2019 · 1 comment · Fixed by #61
Labels
enhancement New feature or request
Milestone

Comments

@hughrun
Copy link
Owner

hughrun commented Aug 21, 2019

Who will benefit from your new feature?

  • App users
  • App Maintainers / System Administrators
  • Developers
  • Someone else

Is your feature request related to a problem? Please describe.
Since toots are automated, it's likely that some will include content that would benefit from a content warning.

Describe the solution you'd like
Add a new setting content_warnings that takes an array of strings. These are checked against each post's tags before tooting, and all matching terms are included as a content warning on the toot.

Describe alternatives you've considered
We could simply CW every toot but that seems a bit over the top.

What kind of users will this most benefit?
Mastodon users who don't want to be confronted with upsetting automated toots.

Additional context
Add any other context or screenshots about the feature request here.

@hughrun hughrun added the enhancement New feature or request label Aug 21, 2019
@hughrun hughrun self-assigned this Aug 21, 2019
@hughrun hughrun added this to the Version 1.1 milestone Feb 2, 2020
@hughrun hughrun removed their assignment Mar 1, 2020
@hughrun hughrun changed the title [FEATURE REQUEST] - enable CWs for given tags when tooting Enable CWs for given tags when tooting Mar 14, 2020
@hughrun
Copy link
Owner Author

hughrun commented Mar 14, 2020

possibly do some kind of regex on the title as well? But maybe then we'd have two problems...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant