Re:Automation and the Use of Multiple Accounts
by nradov on Thursday February 22, 2018 @01:35AM
(#16435646)
How would it solve the spam problem? People would just write bots that work through the website by scripting headless browsers.
[ Parent
| on HN ]
Re:Automation and the Use of Multiple Accounts
by mozumder on Thursday February 22, 2018 @01:45AM
(#16435697)
At the browser level you have Captcha, which is a lot more expensive to spam - you need a human somewhere to overcome - than an API.
Re:Automation and the Use of Multiple Accounts
by bdcravens on Thursday February 22, 2018 @02:00AM
(#16435759)
Depends on your definition of expensive. Captcha solving goes for around 1/10 a cent per catcha. (obviously pricier than free, but if you want to blast out 1000 tweets a day, that'd cost you $1)
Re:Automation and the Use of Multiple Accounts
by tedivm on Thursday February 22, 2018 @04:03AM
(#16436279)
You don't need a human for captcha. You can put together software pretty easily now that'll solve some captchas some of the time, and with automation even a 5% success rate means you can still get thousands of accounts.
Re:Automation and the Use of Multiple Accounts
by icebraining on Thursday February 22, 2018 @10:14AM
(#16438050)
They could easily detect and ban accounts that failed 95% of captchas, though.
Re:Automation and the Use of Multiple Accounts
by tedivm on Thursday February 22, 2018 @03:38PM
(#16441162)
The captcha tends to be during signup, not just any general request. Otherwise third party clients wouldn't work at all. So there isn't any "account" with 95% failure, only IP addresses that fit that. However, spreading requests to multiple IP addresses can help get around that, and botnet rental is pretty cheap these days (cheaper than the captcha prices that have been quoted).
Re:Automation and the Use of Multiple Accounts
by icebraining on Thursday February 22, 2018 @04:00PM
(#16441348)
The captcha tends to be during signup, not just any general request. Otherwise third party clients wouldn't work at all
The post that started this thread was about thought experiment of Twitter killing off their API. So that third party clients wouldn't work is a given. And since they wouldn't work, there's no reason why Twitter couldn't show a captcha many more times after signup.