-
-
Notifications
You must be signed in to change notification settings - Fork 516
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
Searches no longer return any results #839
Comments
Twitter has started requiring authentication for the main search endpoint. This even means twitter.com/search requires you to log in. #812 has a replacement. |
Ah, I see. Thank you! |
Fixed in 1ac389e |
I'm still not getting any search results on unofficialbird.com. |
I'm still not getting any search results on unofficialbird.com or any Nitter instance Edit: I use unofficialbird.com as that one always works. It works on Nitter. Can you please fix it on that one? Thank you |
No, that's not my instance, I only run nitter.net |
If the main search endpoint now requires user login, isn't it a safe assumption that the graphql endpoint will soon also require use login? |
Indeed, but it works for now |
As of a few hours ago, searches on my self-hosted instance always return "No items found". I do not appear to be rate-limited, because I can still access profiles and tweets. I was using an older version of nitter in a docker container and have now updated to the latest version that was posted a few hours ago, but the issue is still present. Searching still works on other instances. Is there some kind of search-only rate limit that I've been hit by?
The older version logged the following when running a search:
The newest version has not logged any errors.
The text was updated successfully, but these errors were encountered: