News for hackers. Stuff that matters.
Re:Automation and the Use of Multiple Accounts by mozumder on Thursday February 22, 2018 @01:32AM (#16435628)
What's the use case for Twitter to allow outside write API access?

If twitter banned all API write access, what would be the problem?

The vast majority of people would still use Twitter via the app or their website, and it would obviously solve a lot of spam problem. But do we really need automated emergency alerts that don't filter through a human?

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.
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.

Re:Automation and the Use of Multiple Accounts by threeseed on Thursday February 22, 2018 @01:53AM (#16435726)
Just a few use cases. I suspect there are quite a lot:

1) Allowing a delay between creation and posting e.g. Buffer.

2) Posting updates to Twitter whenever CMS content changes e.g. Wordpress.

3) Large companies who need tools that work across all social media sites e.g. Hootsuite.

4) RSS -> Twitter.

Re:Automation and the Use of Multiple Accounts by AznHisoka on Thursday February 22, 2018 @08:44AM (#16437454)
I think there is an argument that automating tweeting leads to more spam even though there are some legitimate use cases.

The NYTimes automating tweeting a link to an article after its published provides value. Yet that same functionality allows spammers to tweet links to their spam automatically as well.

Likewise with scheduling, etc.

Anecdotally, before 2010 (when scheduling tweets became popular) I remember Twitter being much more active and discussion oriented, hence I paid more attention to my feed. Now i only use Twitter to search for specific things (ie is AWS down)

Re:Automation and the Use of Multiple Accounts by mozumder on Thursday February 22, 2018 @01:57AM (#16435745)
Those all are automated spam, and doesn't really facilitate discussion. They just increase noise on the platform.

Edit: Reminder that Twitter filters out posts that don't receive much interaction.

Re:Automation and the Use of Multiple Accounts by vidarh on Thursday February 22, 2018 @02:11AM (#16435795)
Pretty much none of what I use Twitter for is discussion. You're assuming everyone uses Twitter for a very specific, limited purpose.
Re:Automation and the Use of Multiple Accounts by threeseed on Thursday February 22, 2018 @02:05AM (#16435783)
Not everything in Twitter is about discussion.

Much of the platform is dedicated to users wanting to follow products, brands, services etc. For them the services I listed are a critical necessity. You can argue all of it is spam but then by that definition so is most of the web.

Re:Automation and the Use of Multiple Accounts by exolymph on Thursday February 22, 2018 @02:04AM (#16435779)
Lol @ you assuming that anything a company posts is spam. You can just unfollow them.
Re:Automation and the Use of Multiple Accounts by RandomInteger4 on Thursday February 22, 2018 @01:46AM (#16435703)
Why would they completely limit API write access when there's a less nuclear route to prevent abuse as detailed in the article?
Re:Automation and the Use of Multiple Accounts by talaketu on Thursday February 22, 2018 @01:57AM (#16435746)
for example, the tweets by @newsycombinator are posted via API.
Re:Automation and the Use of Multiple Accounts by mozumder on Thursday February 22, 2018 @01:59AM (#16435756)
And if you look at that account there's no real interaction going on with it for an account that has 175k followers.
Re:Automation and the Use of Multiple Accounts by vidarh on Thursday February 22, 2018 @02:13AM (#16435798)
And yet it has that many followers, some portion of presumably see some utility in receiving those tweets, even if that utility does not match your idea of what they should do with it.
Re:Automation and the Use of Multiple Accounts by mozumder on Thursday February 22, 2018 @02:15AM (#16435806)
Accounts that don't have interaction get filtered out by Twitter in their timeline.
Re:Automation and the Use of Multiple Accounts by vidarh on Thursday February 22, 2018 @02:54AM (#16435986)
They show up just fine in mine.