It looks like Twitter sometimes uses /i/web/status/<id> URLs that get rewritten incorrectly.
When I look at a retweet of https://twitter.com/_x_takes_/status/1612900253677621251 in Feedly, it contains the broken link https://nitter.net/twitter.com/web/status/1612900253677621251 and the first image from the original tweet.
The original tweet looks like this in https://nitter.mask.sh/_x_takes_/rss:
Nitter seems like it may not handle Twitter's weird /i/web/ URLs properly: https://nitter.net/i/web/status/1612900253677621251 returns an error, while https://twitter.com/i/web/status/1612900253677621251 seems to produce the same content as https://twitter.com/_x_takes_/status/1612900253677621251.
I take that back; https://nitter.net/i/web/status/1612900253677621251 is functional, but it returns a "Tweet not found" error about half the time that I try to load it. :-/
It looks like Twitter sometimes uses
/i/web/status/<id>
URLs that get rewritten incorrectly.When I look at a retweet of https://twitter.com/_x_takes_/status/1612900253677621251 in Feedly, it contains the broken link
https://nitter.net/twitter.com/web/status/1612900253677621251
and the first image from the original tweet.The original tweet looks like this in
https://nitter.mask.sh/_x_takes_/rss
:It seems like some Nitter instances use their own hostnames in these URLs rather than
nitter.net
, but the URL structure is otherwise the same.Here's what it looks like after the proxy converts it to a JSON feed (this is from a different Nitter instance that uses its own hostname):
Nitter seems like it may not handle Twitter's weird
/i/web/
URLs properly:https://nitter.net/i/web/status/1612900253677621251
returns an error, whilehttps://twitter.com/i/web/status/1612900253677621251
seems to produce the same content ashttps://twitter.com/_x_takes_/status/1612900253677621251
.