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 ability to mark statuses as sensitive from reports in admin UI #17668

Merged
merged 2 commits into from
Mar 1, 2022

Conversation

Gargron
Copy link
Member

@Gargron Gargron commented Feb 28, 2022

Using status editing from #16697, make it work across federation.

image

Change "Posts that have been found in violation:" to "Posts cited:" to make notifications less ominous.

@Gargron Gargron added the moderation Administration and moderation tooling label Feb 28, 2022
@Gargron Gargron force-pushed the feature-mark-as-sensitive-from-reports branch from 82306f3 to 2b9ad43 Compare February 28, 2022 12:27
Copy link
Contributor

@ClearlyClaire ClearlyClaire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I would have preferred something more lightweight, without generating a strike or an email, but it works.

One change I would like, though, is allow that feature not only for toots with media attachments but also for toots with preview cards.

Copy link
Contributor

@ClearlyClaire ClearlyClaire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, although I think I'd prefer “Relevant posts:” rather than “Posts cited:” which sounds odd to me.

Also I would have preferred a more lightweight way that did not involve strikes, and maybe improved discoverability (previously, this was right in the statuses list page, now this is in the report page, and it's not clear beforehand that reporting gives the option to mark as sensitive), but that can come later.

Otherwise, this looks good.

sensitive: From now on, all your uploaded media files will be marked as sensitive and hidden behind a click-through warning.
silence: You can still use your account but only people who are already following you will see your posts on this server, and you may be excluded from various discovery features. However, others may still manually follow you.
suspend: You can no longer use your account, and your profile and other data are no longer accessible. You can still login to request a backup of your data until the data is fully removed in about 30 days, but we will retain some basic data to prevent you from evading the suspension.
get_in_touch: If you believe this is an error, you can reply to this e-mail to get in touch with the staff of %{instance}.
reason: 'Reason:'
statuses: 'Posts that have been found in violation:'
statuses: 'Posts cited:'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“Relevant posts”?

@Gargron Gargron merged commit 25d3dc4 into main Mar 1, 2022
@Gargron Gargron deleted the feature-mark-as-sensitive-from-reports branch March 1, 2022 21:20
atsu1125 pushed a commit to atsu1125/mastodon that referenced this pull request Nov 10, 2022
…astodon#17668)

* Add ability to mark statuses as sensitive from reports in admin UI

* Allow mark as sensitive action on statuses with preview cards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
moderation Administration and moderation tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants