-
Notifications
You must be signed in to change notification settings - Fork 49
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
scraper.getTweet returns 404 #49
Comments
I have the same problem with twitter-scraper/src/profile.ts Line 148 in 1a58399
https://twitter.com/i/api/graphql/SAMkL5y_N9pmahSw8yy6gw/UserByScreenName I'm not sure if it's a correct URL but at least it doesn't fail. But now this line fails Line 122 in 1a58399
and I have no idea how to find a correct url |
|
From other projects it appears using the guest token to fetch from these APIs no longer works and you'd have to switch to oauth1.0. Nitter for example is generating temporary anonymous guest users and hitting the above apis with oauth key/secrets. |
There are still some tweet-related functions that are broken, but most of the breakages have been fixed in v0.6.0. Looks like it was entirely just API endpoints that were changed/added/removed all at once. I still need to figure out what's up with replies, though ( |
More fixes in #62, the only thing that still isn't working is tweet threads. |
Unrelated to threads, but I've seen other libraries using this endpoint: May or may not be useful, thought I'd share it anyways. |
@dandyraka have you figured out the problem for getProfile? I'm having troubles currently as the wait time is very long |
@Owen3H what other libraries? Can you share few links? |
I got that specific query from Rettiwt, but there are some others using the twitter-openapi-typescript |
On v0.5.0, using code that worked 2 days ago, I now only get 404 errors when using scraper.getTweet. For example, trying to retrieve https://twitter.com/elonmusk/status/1689963696703848449. Tested on a VPN to check if I was blocked or something but same result. Headers also seem to indicate that it's not a rate limit issue ('x-rate-limit-remaining': [ '499' ])
Can you replicate this or is it a local issue? I'd imagine it's just part of the ongoing Elon Musk self-destruct situation, but maybe you have an idea of how to fix it or what causes it.
Using code
Error (I removed some parts from the passthrough and the URL, but most of the information is there)
The text was updated successfully, but these errors were encountered: