-
Notifications
You must be signed in to change notification settings - Fork 715
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
Twitter searches fail with blocked (403)
#846
Comments
Yeah, the exact error is indeed new, but this is effectively #834. |
blocked (403)
The |
This comment was marked as spam.
This comment was marked as spam.
There is no need to repeat 'me too!!1!'. Yes, everyone is affected at the moment. |
yes for some reason |
so basically twitter search is no longer available, only available to logged in users. Is there a way of doing the same searches while being logged in? maybe by providing tokens/cookies/email&pass? |
Are there any solutions being explored at the moment? Or any temp fixes anyone discovered? |
:f: in chat for twitter search. Search now redirects to login. @JustAnotherArchivist i hope we as a community find another way in, but thank you so much for the hard work you have put into this |
I think it would be a really good idea to fix snscrape to work once the user logs in and improve it to post auto messages, add follow/unfollow features, etc. taking care of the limits of Twitter, in this way the tool would not be forgotten. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
It seems that it's now coming to an end. Fck elon musk ngl, fcked my journey. https://nitter.net/search?f=tweets&q=testing&since=&until=&near= Nitter seems working for searches ! (maybe a hope for a future workaround) |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
The eagle has landed. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry just wanted to as a question. I might just be confused, but what I understand is that we're not able to search by keyword with the new API right? Is there a different way to extract from the API or Twitter isn't allowing any of the search functions? |
@engrCoy Yeah, you misread that. Searching for tweets works now except for a few unsupported filters like One general word of caution: the new API is even more unreliable than the old one; you will regularly see scrapes terminate early for no apparent reason. |
@JustAnotherArchivist I appreciate the clarification on that, and also the precaution about the unreliable output due to an abrupt termination. As for the use of keywords I tried using that on a sample code that I made(please refer to the code attached
|
That search works fine for me with the latest dev version. If that's what you're using, yes, please file a complete bug report. |
Will do, thank you so much! |
Can you elaborate a bit about the Dev version?
|
you can see following post - https://stackoverflow.com/questions/19042389/conda-installing-upgrading-directly-from-github |
@anchitshrivastava It's explained in the README. |
helloo i am sorry but i am using snscrape version 0.6.2.20230320 and still does not work for me the search should i do an update? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Use git version.
|
That worked for me! Issue resolved. |
thank you so much guys it works for me now @JustAnotherArchivist Thank you for your work |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
As already mentioned, the fix is currently only available in the development version. A new release will be made soon if it turns out there are not too many sharp edges. There are also a few unrelated things I want to implement/fix first. To upgrade your existing installation to the latest development version until then, use:
I will lock this issue now since the bug is fixed. Please file a complete bug report if you still experience problems not described above. |
OS: macOS Venture 13.3.1
Python Version: Python 3.8.3
snscrape Version: snscrape 0.6.2.20230320
snscrape module: snscrape.modules.twitter -> TwitterSearchScraper
Bug log:
Original Code:
Note: The code was working a couple days ago and now it gives me this error again. I did try to search bitcoin as keyword in twitter and it worked fine. Sorry in advance if I made any duplicated issue report. I haven't seen a 403 error here.
The text was updated successfully, but these errors were encountered: