Twitter API changes #271
Comments
|
looks like it :( |
|
I don't wish to over dramatize the situation but it feels like I have just been kicked in the CLI. |
|
So is this the end of that? I can't believe that they would just do this, are there no alternatives? |
|
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 . |
|
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 |
|
a couple CLI alternatives which work for now at least.. |
|
The account activity now is premium or business only, and the subscription price is just ridiculous. More info here: 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. |
|
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 :) |
|
Seems a possible workout. It has 15 requests per window rate limit. So basically refreshing per minutes should work |
|
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. |
|
Anything further on a workaround or plan of action? Is this dead in the water and if so, what alternatives, if any? Thanks. |
|
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>.
|
|
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?
|
|
I've been curious if this is the reason why i'm unable to run rainbowstream via the command alone. Whenever I enter 'rainbowstream', it returns the following
I thought this may have been related to generating a new authentication, but is has persisted each time I have tried launching or reinstalling/re-authenticating over multiple days. Is there a specific command I have to use to launch now that the old API is dead? I couldn't get any like 'home' to work as rainbowstream fails to load and returns me to the zsh prompt after that message. Can make a separate issue if this is unrelated, but seeing as how others may still be able to use theirs I wondered if it had any relation to the API switch. |
I'm interested in the answer too xD |
|
As a holdover for those of us that can't use rainbowstream to stream our twitter timelines to the terminal: https://www.howtogeek.com/117306/how-to-follow-a-twitter-feed-in-your-rss-reader/ Then use a terminal rss reader |
|
This is sad |
|
So if I'm following what's going on correctly, Twitter discontinued the
"stream" APIs, but the REST based APIs are still accessible. If true and
the lack of the stream APIs are just the reality of things now, shouldn't
the focus going forward be connecting the client to the available APIs and
moving from a stream experience to a interval based "polling" experience.
I will morn the loss of real time updates and curse Twitter for removing
them, but I think rainbowstream is still a valuable enough command line
tool to just abandon. The patient can still be saved!
…On Fri, Oct 19, 2018 at 9:19 AM silvernode ***@***.***> wrote:
This is sad
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#271 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUO2c9JXWHiwDo_qRbEjTBQlB9Ia3zbks5umft1gaJpZM4WAR0E>
.
|
|
RIP |
|
Been using oysttyer for the past couple months and I find now that I just miss most of my tweets, RS was soo much better, please tell me someone is working on making this poll for changes rather than using the streaming api ??? |
|
Nobody seems to be working on that. |
|
bitlbee's twitter is not too shabby |
|
plz let the rainbow stream again |
|
R.I.P. this is bad joke! |
|
@orakaro I am considering rewriting this myself to use polling, would like to know your opinion on it first though as it obviously breaks the whole streaming concept idea behind rainbowstream.. please let us know if you plan to support this product in the future !? |
|
Sorry for so late reply. Yes I will definitely appreciate someone can make polling happens. Just send PR! |
|
So anything further, or is this the end of Rainbowstream? Sorry to bump this. |
|
I'm currently looking into this, I assume otheras are as well. If I get anywhere I'll send a PR. |
|
So depressing to google "twitter linux terminal clients", come across rainbowstream, get excited by all the great reviews, follow the instructions (spent extra time resolving the missing .rainbow_config.json issue), running the app, getting excited by the interface, getting the "connection problem with API now" error, googling that, and only coming across this thread at the end of that whole process. Would be AWESOME to have the current status (and maybe a link to this thread) here: and maybe here: I'm so excited by this project, I'll be watching this space for updates! 🤞 |
|
You are not the only one, I spent hours to setup it with my custom
linux and then I got the very same warning from Twitter API.
Hopefully `rainbowstream` will reborn from ashes soon! ;D
…On 3/9/19, Jeff Beam ***@***.***> wrote:
So depressing to google "twitter linux terminal clients", come across
rainbowstream, get excited by all the great reviews, follow the instructions
(spent extra time resolving the missing .rainbow_config.json issue), running
the app, getting excited by the interface, getting the "connection problem
with API now" error, googling that, and only coming across this thread at
the end of that whole process. Would be AWESOME to have the current status
(and maybe a link to this thread) here:
https://github.com/orakaro/rainbowstream
and maybe here:
https://rainbowstream.readthedocs.io/en/latest/
I'm so excited by this project, I'll be watching this space for updates!
🤞
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#271 (comment)
--
PGP Key ID: 0x3F75FA35
|
|
@threecleartones @deepcell Really sorry about that. Updated README 🙇 |
|
So, approaching 10 months since Rainbowstream lost it's ability to update itself realtime, is anything further going to transpire or is this truly dead in the water? Thanks. |
|
Sounds like it's officially dead to me which is sad. I wish they would just put a bullet through it's head already instead of keeping us holding on. It was the best twitter client hands down no matter what platform/OS you used. |
|
I say that Rainbowstream should rebrand and Target open alternatives to
Twitter like Mastodon and stop relying on centralized services like Twitter
that tend to change their mind on a dime. I think that's the only way to
keep this project somewhat alive.
…On Sat, Jun 1, 2019, 15:43 MystikSpiral ***@***.***> wrote:
Sounds like it's officially dead to me which is sad.
I might be wrong but it looks like Twitter is wanting to charge for API
access for certain things now which would mean Rainbowstream would no
longer be free.
I wish they would just put a bullet through it's head already instead of
keeping us holding on.
It was the best twitter client hands down no matter what platform/OS you
used.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#271?email_source=notifications&email_token=AADCENDRZ45BM4CAAXGZCZTPYL3RZA5CNFSM4FQBDUCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXJ4SY#issuecomment-497983051>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADCENDHB6YFM56ZI6Z4DPTPYL3RZANCNFSM4FQBDUCA>
.
|
|
@silvernode that already exists as tootstream, which was inspired by rainbowstream https://github.com/magicalraccoon/tootstream |
|
Yeah, I use tootstream though I still like Rainbowstream much better
because of the UX which is not exactly the same as tootstream.
…On Sat, Jun 1, 2019, 20:19 StarlitGhost ***@***.***> wrote:
@silvernode <https://github.com/silvernode> that already exists as
tootstream, which was inspired by rainbowstream
https://github.com/magicalraccoon/tootstream
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#271?email_source=notifications&email_token=AADCEND37RS36ZYONCWRSD3PYM33RA5CNFSM4FQBDUCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXM3DA#issuecomment-497995148>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADCENDVI55Q67F6WJXFHMTPYM33RANCNFSM4FQBDUCA>
.
|
|
Hello guys, here is a good news: I succeed in an attemp to make RainbowStream's stream live again using a polling strategy! Here is some notes
|
|
Let's consider this as a beta state. Please report any bug/problem 🙏 |
|
Awesome news. |
|
Works great! Thank you! |
|
So amazing! Thanks!! |
|
Thanks. It is working just great. I actually prefer that it is not updating the stream in real-time. It is much more readable during periods of high activity. |
|
I'm getting 'Rate limit exceeded'. It even hasn't started in the first place. |
|
i am having the same problem...rate limit exceeded |
|
Also getting rate limit exceeded |
|
Great Work!! |
|
still having this problem |
and others
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
The text was updated successfully, but these errors were encountered: