-
Notifications
You must be signed in to change notification settings - Fork 34
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
#myTimeHasCome #12
Comments
Seems to be affecting most instances, but not all. I can use Twint with this instance for example. |
Heh, looks like it's already fixed! zedeus/nitter#840 (comment) |
Please don't scrape public Nitter instances, it's unethical and can cause a worse experience for people actually using them properly. Host your own on your computer/server, it takes a few seconds to set up with Docker and a few minutes at most without. |
@zedeus totally agree with you. I just added a line in the README doc |
Does this new variant of Twint still work? I am a former Twint user who, after this tool no longer works, has searched for alternatives and I have come back to you. However after reading these messages I don't know if this new tool is still working. |
It's in a bit of a weird state. With the rapid changes Twitter has been making recently to try to cut off web scraping, Nitter (which this project relies on) is on-off working. Some instances are down because they're rate-limited, which this issue refers to. Although that issue has been fixed for instances that have updated. There was also a recent change that made search an authenticated-user-only action, effectively bringing down Nitter's search functionality unless you used a fork that added the ability to set an access token. But that seems to have been reversed, at least temporarily. It's a cat and mouse game basically and is currently working. But for how long, nobody really knows. |
as of now this tool doesn't because the bridge between Nitter and Twitter is broken.
I will add details here as time goes by.
* heavy sad noise *
The text was updated successfully, but these errors were encountered: