Should have been, we have not noticed any issues with chatme.im so far.
On Wed, Feb 13, 2013 at 4:46 PM, Per Gustafsson <[email protected]> wrote: > We have noticed any issues with chatme.im so far. > > > On Wed, Feb 13, 2013 at 4:42 PM, Thomas Camaran <[email protected]> wrote: > >> hi, with chatme.im all ok? >> >> >> 2013/2/13 aszlig <[email protected]> >> >>> On Wed, Feb 13, 2013 at 09:48:59AM +0100, Per Gustafsson wrote: >>> > I work with Google's chat service, and we are seeing lots of spammy >>> invites >>> > from users on various federated domains, including jabberes.org, >>> jabber.se, >>> > jabber-hosting.com and jabber.org. Have you noted an elevated amount >>> of >>> > sccount creation etc., and is there anything you can do about it in >>> that >>> > case, otherwise we will have to institute very tight limits of invites >>> per >>> > day being sent from federated domains. >>> >>> Here I've got the same problems as well (aszlig.net, headcounter.org, >>> no-icq.org, noicq.org - not yet listed at xmpp.net since the rework) and >>> i'm going to disable new registrations as soon as the load is low >>> enough. The main target of these massive spammy subscribes is gmail.com >>> and it's quite hard to track them down without "accidentally" locking >>> out real users. >>> >>> My second step would be to reenable registrations and only allow >>> verified users to use S2S. But I'm not sure about how to do this for >>> every single user (maybe some kind of WoT within the local network?). >>> >>> So, any idea about how to mitigate this without forcing too much >>> restrictions on real users (like for example I'd want to avoid >>> captchas)? >>> >>> a! >>> -- >>> aszlig >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.10 (GNU/Linux) >>> >>> iF4EAREIAAYFAlEbtEIACgkQ0OvQ7IwtyWHDvwD/bdpv4M//fOBDVpiaV6sQjMQm >>> gRCbQvTEaramaFj+X/oBAKLo1zCVaE3sOuyagWhnlcn5kQP9nwJPW1BaTvXcb6p7 >>> =oXrV >>> -----END PGP SIGNATURE----- >>> >>> >> >
