-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/23/13 10:57 AM, Alex Hanselka wrote:
> On 5/23/2013 10:22 AM, Kevin Smith wrote:
>> The best advice I can give is not to allow unprotected (i.e.
>> without a captcha or similar) inband registration, as people use
>> scripts to autoregister account
On 5/23/2013 10:22 AM, Kevin Smith wrote:
> The best advice I can give is not to allow unprotected (i.e. without a
> captcha or similar) inband registration, as people use scripts to
> autoregister accounts across many servers using IBR. If you require
> registration through a web page with captcha
On 23 May 2013 11:15, Peter Saint-Andre wrote:
> At jabber.org, we turned off in-band registration and forced all users
> to register via https://register.jabber.org/ with CAPTCHA required.
> That did not really prevent spam registrations (at one point we had
> over 10,000 users that we suspected
On Thu, May 23, 2013 at 4:36 PM, Kevin Smith wrote:
> There are also likely options along these lines that involve less
> privacy invasion than operators manually examining the accounts. A
> captcha for every subscription request? Only one outstanding (not
> reciprocated) roster request at a time
On Thu, May 23, 2013 at 4:28 PM, Jonas Wielicki
wrote:
> I know that this proposal is kind of dangerous as it requires
> introspection of the users messages.
>
> But how about this: After registration, the users is put on a
> surveillance list, for like a few days or weeks. She shall be notified
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/23/13 9:28 AM, Jonas Wielicki wrote:
> I know that this proposal is kind of dangerous as it requires
> introspection of the users messages.
>
> But how about this: After registration, the users is put on a
> surveillance list, for like a few da
I know that this proposal is kind of dangerous as it requires
introspection of the users messages.
But how about this: After registration, the users is put on a
surveillance list, for like a few days or weeks. She shall be notified
about this, in the Terms of service and possibly by a system tool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/23/13 9:22 AM, Kevin Smith wrote:
> On Thu, May 23, 2013 at 8:39 AM, Alex Hanselka
> wrote:
>> Do you guys have any tips for spam registrations for open
>> servers? I'm running one that eventually I'll add back to the
>> list on xmpp.net but befo
On Thu, May 23, 2013 at 8:39 AM, Alex Hanselka wrote:
> Do you guys have any tips for spam registrations for open servers? I'm
> running one that eventually I'll add back to the list on xmpp.net but before
> I do I wanted some tips on this :)
The best advice I can give is not to allow unprotected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/23/13 1:39 AM, Alex Hanselka wrote:
> Heya!
>
> Do you guys have any tips for spam registrations for open servers?
> I'm running one that eventually I'll add back to the list on
> xmpp.net but before I do I wanted some tips on this :)
>
> Thanks
Heya!
Do you guys have any tips for spam registrations for open servers? I'm
running one that eventually I'll add back to the list on xmpp.net but
before I do I wanted some tips on this :)
Thanks for any insight!
Alex
11 matches
Mail list logo
