Instances Constantly Not Working

[iitzRichie]

Idk if it's maybe something on my end, but Instances constantly don't work. I'll get only a few uses before I get a "This site can’t be reached" message, and then I have to switch to another Instance, and rinse-repeat. And checking the wiki and looking at their uptime and health, they appear to be fine.

To give an example: nitter.salastil.com is rated second on the wiki as being pretty healthy, but this Instance in particular gives me nothing but problems.

[markcellus]

Good to know those uptimes aren't as accurate. Anyone know how they are being calculated?

[zedeus]

The status page requests Twitter accounts via the Nitter instance and verified the content is valid, so they are accurate and do reflect actual uptime. The error you're describing sounds more like a 403, which would get triggered if you're trying to scrape these and you hit a rate limit. What status code is returned? Check the network tab using devtools in your browser of choice.

[iitzRichie]

The status page requests Twitter accounts via the Nitter instance and verified the content is valid, so they are accurate and do reflect actual uptime. The error you're describing sounds more like a 403, which would get triggered if you're trying to scrape these and you hit a rate limit. What status code is returned? Check the network tab using devtools in your browser of choice.

It's a 403 error, yes. I'm just looking up accounts throughout my day though. I'm not doing anything else besides typing in Nitter.net/[account name] in my browser and reading the tweets posted by said account. I might do this for like 3 accounts before I'm given that error and then I have to switch to another instance. But is this not the point of Nitter? I'm only using Nitter in the same way I used Twitter.

[ArchivingToolsForWBM]

For me, currently I noticed that https://nitter.privacydev.net/ takes forever to load images, then get hit with a 504 Gateway Time-out. Not sure if its nitter server having issues, or twitter upped its anti-scraping measures even on media URLs.

[iitzRichie]

For me, currently I noticed that https://nitter.privacydev.net/ takes forever to load images, then get hit with a 504 Gateway Time-out. Not sure if its nitter server having issues, or twitter upped its anti-scraping measures even on media URLs.

I get this as well. Media is a big struggle for me with Nitter. I opened a report about this as well, but basically you just gotta instance hop if one isn't working so well.