Harrasment, for #310 and #311 #328
Conversation
to abuse mitigation.
Also closes #311
|
Commenting here as I was also going to suggest to rename this section to "Abuse". The principle explicitly refers to the notion of "abuse", while the text defines "harrasment" and "unwanted information". Would it be possible to have a more explicit definition of "abuse" that the principle could then link to? |
|
Thanks for the feedback @tidoust!
If we merge these changes and the rename, I think it'll be better to then open a new issue for adding the definition, so we don't block the editorial changes on it. |
Co-authored-by: Jeffrey Yasskin <[email protected]>
rhiaro
added
agenda+
|
One suggestion remaining for the group to address, then ready to merge. |
| Systems that allow for communicating on the Web must provide an | ||
| effective capability to report abuse. [=User agents=] and [=sites=] must | ||
| take steps to protect their users from abusive behaviour, and abuse | ||
| mitigation must be considered when designing web platform features. |
There was a problem hiding this comment.
This consolidation of principles applies different kinds of obligations to different actors. Designing reporting systems is quite different from abuse mitigation in the design of web platform features.
There was a problem hiding this comment.
We split this principle into two in the meeting today, which I think fixes this comment.
Co-authored-by: Daniel Appelquist <[email protected]> Co-authored-by: Amy Guy <[email protected]>
SHA: a501426 Reason: push, by jyasskin Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Unwanted Information and Harassment seemed to be saying a lot of the same things. I've merged the principles, but retained the definitions. Renamed the section to "Abuse". I feel it shortens and simplifies things, but interested to hear what others think. Let me know if I lost anything.
See #321 for edits in context.
Preview | Diff