Closed Phoenix616 closed 4 years ago
Thanks for the heads up. That may be related to Twitter shutting down several API endpoints. Investigating.
@muesli, I was able to post to Twitter, but the beehive process takes 100% CPU (stopping the Twitter Bee fixes that until you turn it back on again)! Were you already able to take a look at the Twitter Hive? Reacting to Twitter likes also didn't seem to work for me, Last Event
always says never
for me.
@muesli, the only thing that runs infinitely in the Twitter Bee seems to be:
Although item
seems to be nil
a lot (all the time?).
I was able to fix the 100% CPU problem, but reacting to a like still doesn't seem to work for me. At least posting tweets is still working...
Last commit on https://github.com/ChimeraCoder/anaconda (library that handles the Twitter API) was 2 years ago. 😬 There is also https://github.com/dghubble/go-twitter, which is almost as inactive, but also has it's issue tracker disabled and a lot of open PRs...
The user stream https://userstream.twitter.com/1.1/user.json is retired since more than 2 years.
The replacements seem to be the "Premium Account Activity API" and "Enterprise Account Activity API". 😁 At least posting tweets still seems to work.
Yeah, I guess most people stopped using the Twitter API at that point, myself included. I'm actually one of the anaconda maintainers, but development has pretty much ceased when Twitter shut down most of their API for public use.
Posting still works (and I plan to use it), only the user stream is shut down.
I've just removed the user stream from the Twitter hive, as it's not supported by Twitter anymore. This in turn means the TwitterBee now only supports posting, following & unfollowing other users. There are no more events we can currently support. What a shame.
This also fixes this issue.
Awesome, @muesli! Are you also pushing the changes to Docker-Hub so I can use your container again? 😁
If you use beehive:latest, this will automatically be built every time someone pushes to git master.
image: fribbledom/beehive
should get the latest, thank you very much!
If thats resolved, please consider updating https://github.com/muesli/beehive/wiki/Twitter
It seems to be using 100% of one core/thread once I enable a Twitter bee even without using any kind of chain which would react on twitter actions (I only use it to send tweets)