Twitter API changes

[xxKeith20xx]

We have connection problem with twitter stream API right now :(
The Site Streams and User Streams endpoints have been turned off. Please migrate to alternate APIs. See https://t.co/usss

So... is that the end for apps like this? ;c

[jokebroker]

looks like it :(

[yipmanfan]

I don't wish to over dramatize the situation but it feels like I have just been kicked in the CLI.

[johnpiers]

So is this the end of that? I can't believe that they would just do this, are there no alternatives?

[xxKeith20xx]

Not a solution but more of an alternative to Twitter all-together. There are a few Mastodon command line apps that are in active development: https://github.com/ihabunek/toot .

[mikeofmany]

I suppose if someone is up for refactoring the api calls, https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference/site-stream

[cirrusUK]

a couple CLI alternatives which work for now at least..
https://github.com/bear/python-twitter #twitter -R 4 -r 'refresh every 4 seconds'
https://github.com/piroor/tweet.sh #./tweet.sh post 'status message'
https://github.com/oysttyer/oysttyer # http://oysttyer.github.io/docs/userGuide.html#commands-user

[orakaro]

The account activity now is premium or business only, and the subscription price is just ridiculous. More info here:
https://twitter.com/orakaro/status/1030785576973217792

Basically it is impossible for an opensource project.

Right now we can still use RS as a commandline client, but the stream need to be reconsidered carefully. Sorry about all of this.

[movalex]

Is it possible to force RS to automatically refresh timeline every, say, minute or so? Realtime streaming is not that important afterall. Also we can change the name to just Rainbow :)

[orakaro]

Seems a possible workout. It has 15 requests per window rate limit. So basically refreshing per minutes should work

[IngwiePhoenix]

Ouch. I was about to post an issue here - and ran across this issue ticket. I am actually very surprised that they are cutting these endpoints. After all - they do have a ton of servers to balance all these requests. Any idea why they did that?

Requesting per minute to keep the stream updated is at least an alternative - less interactive, but it at least allows to keep most of the behaviour. Direct Messages don't seem to be that affected by the API changes, at least not in the same way as the streams are. Which is...kinda confusing.

[johnpiers]

Anything further on a workaround or plan of action? Is this dead in the water and if so, what alternatives, if any? Thanks.

[IngwiePhoenix]

See the link about the Twitter API that has been posted here and shown in the console too. Twitter "gracefuly" disabled streaming APIs - so even if there were alternatives, well, then there "were" alternatives. With the streaming API gone, all we can do is set a refresh time - and thats it.

…

Am 26.09.2018 um 10:49 schrieb John Piers Cilliers ***@***.***>: Anything further on a workaround or plan of action? Is this dead in the water and if so, what alternatives, if any? Thanks. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#271 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACwnlOyn5RgYO58BrWFpPy97O6hmOAv8ks5uez-PgaJpZM4WAR0E>.

[movalex]

Is it possible to set auto-refresh time in current version? I'd like it to refresh every minute, and preferably with no warnings from Twitter about Site Streams have been turned off. Ideally those ID's showed after refresh has to be unique. Is it hard to implement?

See the link about the Twitter API that has been posted here and shown in the console too. Twitter "gracefuly" disabled streaming APIs - so even if there were alternatives, well, then there "were" alternatives. With the streaming API gone, all we can do is set a refresh time - and thats it.