nitter
nitter copied to clipboard
zedeus
Nitter search no longer presenting results.
The endpoint has started returning 404 Not Found, I don't know if this was intentionally done.
I think the endpoint might still be here. If you visit the url through your browser you get a 403 error. Something must have changed in the request process...
When you're logged in Twitter, if you copy the request to https://twitter.com/i/api/2/search/adaptive.json as a cURL it still works tho. I got it to work in a simple shell script where I update the cursor and call the endpoint again, but you get rate limited quickly!
Elon Musk restricted search to registered accounts
https://9to5mac.com/2023/04/26/twitter-restricts-search-fleets-coming-back/
Could maybe replace the search with a ddg (or whatever engine) filter search like for example:
search term site:twitter.com
Not sure how it would work out making a Twitter account and running all nitter search queries over it though?
if a search engine is use instead of twitter's search, you lose access to all filters such as minimum amount of likes, retweets, exclude retweets…
twitter-api-client on PyPI was updated 3 hours ago: does it fix the problem with search?
Based on the issues, unfortunately, no:
Searchwill now need an email, username, and password just likeAccountandScraper.
It looks to me like #830 from @PrivacyDevel could be a solution for this as well.
It looks to me like #830 from @PrivacyDevel could be a solution for this as well.
Search works fine in their instances, indeed. But beware of the rate limit!
It looks to me like #830 from @PrivacyDevel could be a solution for this as well.
Search works fine in their instances, indeed. But beware of the rate limit!
how to avoid account ban when signed in?
It looks to me like #830 from @PrivacyDevel could be a solution for this as well.
Search works fine in their instances, indeed. But beware of the rate limit!
how to avoid account ban when signed in?
Create accounts that are exclusively used by your Nitter instance that you don't care too much about losing. Or just risk it and hope for the best. I didn't lose any of my accounts yet at least.
yeh, was just an instant idea for that issue that came to my mind. It would still be better than no search at all, right? But account creation for every instance could work, too.
Hi! Found this discussion while looking for potential solutions for my project. I might add that those unofficial tokens (via v1.1 api [I know, yikes.]) Appear to work. Not too sure how long but it could be a solution.
This is working again? At least multi user feeds are: https://nitter.net/ap,cnn
Oh nice, I guess Twitter reinstated the new GraphQL API we use. I didn't change anything, and it seems likely they will break it again in the near future, but enjoy it while it lasts!
@zedeus can you point out to the exact code where you interact with GraphQL? Thx!
Hi! Found this discussion while looking for potential solutions for my project. I might add that those unofficial tokens (via v1.1 api [I know, yikes.]) Appear to work. Not too sure how long but it could be a solution.
I tried implementing the graphQL version on my local version. It works for a number of users I tried but unfortunately it doesn't do shadowbanned/Age restricted(?) users.
For other routes they all are gated at maximum of X amount tweets or to that effect. A potential solution would be to try and scrape the entirety of twitter. But I personally don't think that is a valid solution when you just want to start with X amount of users first. Anyone has any ideas?
@Ristellise , we can create a group and split that 40k+ per month bill for institutional twitter API (but that group should be large lmao)
is working again? i see many instances working 100%
It works again… for now, until “this guy” messes it up again. So, let’s enjoy it as long as we can.
cannot confirm this behavior is happening again, our nitter instance is more or less functioning as normal
some searches seem kind of broken. for example searching gun didn't work but NASA did on first search, second search the results were the opposite and gun worked but NASA didn't. I think they're just actively working on something imo