Zed

No, just more bot swarms causing rate limits.

Probably not, we'll see.

Nitter doesn't use the APIs in the normal way with developer credentials, so I really doubt it would be affected.

I can either add a red "Original tweet" link below the video, or make the username link to the tweet instead of the account. What do you think?

Rate limiting on the old endpoints. #812 fixes it, it'll be merged within the next couple of days, you can try it now on nitter.net

No idea why this is, another host (nitter.nl) with no unnecessary security headers also won't embed.

I guess it's probably due to the IP address/range being blocked by my extensive cloud blocking rules. Any idea which IP(s) they might use to pull embeds?

That's tricky, I don't want to unban GCP ranges because of all the abuse that comes from them, not sure what to do about this.

This was likely a bug on Twitter's side, not sure. Please reopen if you encounter it again.

Search uses a non-GraphQL endpoint, hence why it isn't affected in the same way. I've considered using search for timelines before, but it provides a much worse experience and is...