-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension broken #98
Comments
Ah, I was wondering how long it would keep going after Twitter shut down their API. Thanks for reporting. Looks like this is the end of Treeverse, unless Twitter opens the API up again. |
I thought so. Thanks for creating this extension, and I hope we'll see it working again some day. Of course, if Twitter wouldn't perish by then. :) |
I don't see why this extension needs to use the Twitter API when it can just scrape the page in the browser. Gonna fork and see what I can do. |
It has never used the official API; it used to scrape the page HTML and then moved to reverse-engineering the internal API. My theory is that when the official API got shut down, everybody turned to reverse-engineering the internal API, so the company started cracking down on that and made it basically impossible to do. But you're welcome to try, I hope you succeed! |
> GET https://api.twitter.com/2/timeline/conversation/<tweet_id>.json?include_reply_count=1&tweet_mode=extended
< HTTP/2 429 Too Many Requests
The text was updated successfully, but these errors were encountered: