I don't know if it's just me but I can't seem to view the nitter link, says the tweet isn't found, I can't use the OP Twitter link because I can't see anything without logging in.
I ran across a thread once indicating that the guy who hosts that instance has a bit of a fight on his hands keeping it usable. Frequently fights hoards of bots, that sort of thing. Your signal probably got mistaken for some noise.
We need Nitter and BitTorrent to have a baby, p2p so we can share the load.
IPFS would be a good layer to build this on top of, but IPFS itself doesn't handle the correspondence between URL and CID. As it is, web DOMs are too variable to handle via content addressing.
This would involve eliminating parts of the page that are unlikely to be stable (i.e. ads, pagination based on screen size, session specific details like usernames), and use that for the CID. That way the only time that users end up storing separate copies of the page is when it has actually been changed substantially. You'd probably also need some code to fluff the normalized content back up into something that makes sense for the device you're reading it on.