I agree with Christian.
If we have reasonably effective means to recognize and remove spam
accounts/profiles/teams etc., that's good enough.
On 11/14/2016 1:10 AM, Christian Beer wrote:
I don't think account creation is the right place to fix it. Especially
since it will break older Clients.
Hello,
I've been dealing with huge amounts of spam accounts for
the past few months,
averaging at 500k or more registration attempts weekly. My
project was hit by some kind
of large botnet. I had to modify lots of things but
currently it looks like I'm winning the battle.
Here's what I did +
On 14.11.2016 10:49, Jord van der Elst wrote:
> 3. On the user account, completely visible to all, logged in or not.
> Example in the field:
> https://setiathome.berkeley.edu/show_user.php?userid=20272
>
> This account and its URL can be read by logged in and not logged in
> users. So one can link
3. On the user account, completely visible to all, logged in or not.
Example in the field:
https://setiathome.berkeley.edu/show_user.php?userid=20272
This account and its URL can be read by logged in and not logged in users.
So one can link to this account to get people or things to follow the
Hey,
I like the idea of access control, but not solely for 'known AMs'
because the Gridcoin community plans on creating multiple AMs in the
future (pools=AMs). In the 'spammer account attack' email thread I
suggested a personal RPC/API access code that an user could generate
from their user
On 11.11.2016 22:46, David Anderson wrote:
> The create-account RPC is used by
> - account managers (BAM!, etc.)
> - the BOINC client
>
> If it were just account managers we could add some kind of access control
> (i.e. accept RPCs only from known AMs).
> But this would break the client.
>
> What
