From 7bcd3330e26804cbc98d1c532fed54c352518907 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Mon, 21 Jun 2021 08:13:47 -0400 Subject: [PATCH] XEP-0377: complete rework based on list feedback --- xep-0377.xml | 153 +++++++++++++++++++++++++++++++++------------------ 1 file changed, 100 insertions(+), 53 deletions(-) diff --git a/xep-0377.xml b/xep-0377.xml index 69c18494..82afd9b1 100644 --- a/xep-0377.xml +++ b/xep-0377.xml @@ -13,7 +13,7 @@ &LEGALNOTICE; 0377 - Deferred + Experimental Standards Track Standards Council @@ -26,6 +26,12 @@ NOT_YET_ASSIGNED &sam; + + 0.3 + 2021-06-21 + ssw + Rework based on list feedback. + 0.2 2017-09-11 @@ -49,75 +55,84 @@

Many spam and abuse prevention techniques rely on users being able to report other users who are sending unwanted messages, or specific instances of - abuse. &xep0191; allows users to block spammers, but does not provide a - mechanism for them to report a reason for the block to the server operator. + abuse. + &xep0191; allows users to block spammers, but does not provide a mechanism + for them to report a reason for the block to the server operator. This specification extends the blocking command to optionally provide an abuse report.

+ +

+ This document extends the blocking command instead of providing a separate + reporting IQ because we hypothesize that this will slightly lower the levels + of false reports received by service operators. + We have observed a common pattern on the internet where a user becomes mad + at or disagrees with another user and begins harassing them by replying to + or reporting their every comment even if it is not itself spam or abusive. + However, this sort of behavior cannot continue if the harasser can no longer + read the messages of the person they are stalking. + Giving them a choice between their abusive behavior and being able to + read their targets can possibly force them to break the cycle and only + create valid reports. +

+

- Entities that support &xep0030; and abuse reporting MUST respond to service - discovery requests with a feature of 'urn:xmpp:reporting:0' and with a - feature for each reason supported by the responding entity as described in - the relavant specifications. Eg. a response from a server that supports - reporting and understands the abuse and spam reasons defined later in this - specification might look like the following: + Entities that support &xep0030; and abuse reporting using the blocking + command as defined in this spec MUST respond to service discovery requests + with a feature of 'urn:xmpp:reporting:1'. + Support for this namespace also indicates support for the abuse reporting + reasons defined in this document. + For example, a response from a server that supports reporting and + understands the abuse and spam reasons defined later in this specification + might look like the following:

- - - + + … ]]>

The payload for reporting abuse to the server takes the form of a - <report/> qualified by the 'urn:xmpp:reporting:0' namespace &VNOTE;. - Report payloads are reusable and MUST NOT be sent without first being - wrapped in a stanza. + <report/> qualified by the 'urn:xmpp:reporting:1' namespace &VNOTE;.

]]> +]]>

- Abuse reports MAY include a reason for the report and servers MUST tolerate - unknown XML elements in a report without making assumptions about the - semantic meaning of unknown elements. + Abuse reports MUST include a reason for the report in the "reason" attribute.

This document defines the following reasons for a report:

-
<spam/>
+
urn:xmpp:reporting:spam
Used for reporting a JID that is sending unwanted messages.
 -
<abuse/>
+
urn:xmpp:reporting:abuse
Used for reporting general abuse.
-

- Clients MUST include only one reason per report. -

Reports MAY contain a user provided message explaining or providing context - about the reason for the report. See also the - Internationalization Considerations section of this - document. + about the reason for the report. + See also the Internationalization Considerations + section of this document.

+ Never came trouble to my house like this. - ]]> @@ -127,27 +142,57 @@ For example:

+ - - - - + + ]]>

Servers that receive a blocking command with a report MUST block the JID or - return an error just as they would if no report were present. Servers then - MAY take other actions based on the report, however, such actions are - outside the scope of this document. + return an error just as they would if no report were present. + Servers then MAY take other actions based on the report, however, such + actions are outside the scope of this document.

+

+ If the server supports &xep0313; the report MAY also include the stanza-id + of specific messages being reported. + This is done by including copies of each <stanza-id/> element that the + user wishes to report as a child of the <report/> element. + The stanza indicated by the provided stanza-id SHOULD be by the same JID + being reported and blocked. +

+ + + + + + + + Never came trouble to my house like this. + + + + +]]>

Clients that support sending reports as part of the blocking command SHOULD - expose interfaces to both block a JID without reporting it as abusive, and - to block and report a JID. + expose interfaces to both block a JID without reporting it as abuse, and to + block and report a JID. +

+

+ The blocking command may be used to block multiple JIDs at the same time. + When blocking multiple JIDs any abuse report only applies to a single JID. + If the client allows selecting multiple JIDs in an abuse reporting dialog + they SHOULD also allow choosing a separate reason, text, and messages for + each JID. + They MAY choose to only allow reporting a single JID at a time as well when + the "block and report" dialog is accessed, and multiple JIDs when the + "block" dialog is accessed.

@@ -170,7 +215,7 @@

This specification defines the following XML namespace:

    -
  • urn:xmpp:reporting:0
    • +
  • urn:xmpp:reporting:1

Upon advancement of this specification from a status of Experimental to @@ -188,15 +233,13 @@ All abuse report reason registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in - protocol URNs of the form "urn:xmpp:reporting:reason:name:X" (where - "name" is the registered name of the reason and "X" is a non-negative - integer). + protocol URNs representing the reason.

®PROCESS; - The name of the abuse report reason. - urn:xmpp:reporting:reason:{name}:{ver} + The human-readable name of the abuse report reason. + URN representing the reason. A natural-language summary of the reason. The document in which the report reason is specified. @@ -206,8 +249,8 @@

This specification defines the following abuse reporting reasons:

    -
  • urn:xmpp:reporting:reason:spam:0
    • -
  • urn:xmpp:reporting:reason:abuse:0
    • +
  • urn:xmpp:reporting:spam
    • +
  • urn:xmpp:reporting:abuse

Upon advancement of this specification from a status of Experimental to @@ -216,15 +259,15 @@

- Spam - urn:xmpp:reporting:reason:spam:0 + spam + urn:xmpp:reporting:spam Used to report a JID that was sending spam messages. XEP-0377 ]]> - Abuse - urn:xmpp:reporting:reason:abuse:0 + abuse + urn:xmpp:reporting:abuse Used to report general abuse that is not covered by a more specific reason. XEP-0377 ]]> @@ -243,5 +286,9 @@ Stout, and Matthew Wild. A special thanks to Daniel Wisnewski for giving the presentation that kicked off the anti-abuse work.

+

+ Thanks also (in no particular order) to Jonas Wielicki, Georg Lukas, + Daniel Gultsch, and Matthew Wild for their feedback. +