hypothesis / hypothesis/product-backlog
We don't have good tools to manage flagged annotations across multiple pages or at scale
- Dominant language
- No language data
- Stars
- 122
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Hypothesis ostensibly has tools for moderating annotations. Users can flag annotations, which results in an email notification to group creators. Group creators can then hide flagged annotations. However, we really don't have useful tools for group creators to see and action flagged annotations across multiple pages or handle moderation at any sort of scale.
Every time an annotation is flagged, we send a terse and generic notification message to the group creator:
> An annotation has been flagged. Please visit https://hyp.is/{id}/{slug} for more details.
The group creator has to then click this link and wait for the client to load up before they can even see who wrote the annotation or what the offensive content was. If the moderator decides _not_ to hide a flagged annotation, we don't have any way to record that and thus remove the annotation from the moderation queue.
Contrast this with eg. the [Moderation Panel](https://help.disqus.com/customer/portal/articles/466238) that Disqus has where there is a dedicated interface for moderators designed to make it easy to process a lot of comments quickly.
My suggestion would be that a useful first step would be to make it simply possible to search for flagged annotations via the API. This would enable us to prototype some solutions and may be useful for publishers as well.
----
Some prior art:
**Disqus**: https://help.disqus.com/customer/portal/articles/466238
**WordPress**: https://codex.wordpress.org/Comment_Moderation
**Discourse**: https://meta.discourse.org/t/discourse-moderation-guide/63116#heading--flags
All of the above have some notion of a queue and a dedicated interface for moderators to see details of flagged content and action them conveniently.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.