#myTimeHasCome

[pielco11]

#myTimeHasCome

[archy-bold]

Heh, looks like it's already fixed! zedeus/nitter#840 (comment)

[archy-bold]

Seems to be affecting most instances, but not all. I can use Twint with this instance for example.

[zedeus]

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.

[pielco11]

@zedeus totally agree with you. I just added a line in the README doc

[DavidPerea]

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.

[archy-bold]

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.