From 65aca3d036bb2dfde229038d2cadadeaaf9f3766 Mon Sep 17 00:00:00 2001 From: Ian Paterson Date: Sat, 28 Oct 2006 10:17:57 +0000 Subject: [PATCH] 0.5 RC1 Added reference to XEP-01610.5 RC1 Added reference to XEP-01610.5 RC1 Added reference to XEP-01610.5 RC1 Added reference to XEP-01610.5 RC1 Added reference to XEP-0161 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@128 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0158.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/xep-0158.xml b/xep-0158.xml index 86c10838..e1bb49c1 100644 --- a/xep-0158.xml +++ b/xep-0158.xml @@ -23,6 +23,12 @@ None challenge &ianpaterson; + + 0.5 + 2006-10-30 + ip + Added reference to SPIM Reporting + 0.4 2005-09-30 @@ -532,7 +538,8 @@ -

It is RECOMMENDED that entities employ other techniques to combat SPIM in addition to those described in this document. The expectation is that this protocol will be an important and successful tool for discouraging SPIM. However, much of its success is dependent on the quality of the CAPTCHAs employed by a particular implementation.

+

It is RECOMMENDED that entities employ other techniques to combat SPIM in addition to those described in this document. For example see &xep0161;.

+

The expectation is that this protocol will be an important and successful tool for discouraging SPIM. However, much of its success is dependent on the quality of the CAPTCHAs employed by a particular implementation.

The administrator of a challenger MUST discontinue the use of Robot Challenges under the following circumstances:

  • If he realises that the challenger's challenges are largely ineffective in combating SPIM, and that the reduction in SPIM does not compensate for the inconvenience to humans of responding to the challenger's challenges.