Some digging shows that tweet is totally misinformed. He seems to think that because niftygateway's json response returns an internet-facing url, that the underlying NFT must also be referencing an internet-facing url (as opposed to an IPFS url/hash). This is incorrect. The URL he's seeing in the API response is simply a IPFS proxy service offered by the NFT website. If you extract the identifier of the NFT from the url he linked[1] and plug it to etherscan[2], then scroll down to "trumpVictoryIPFSHash", you can see that the NFT is actually referencing the IPFS hash directly, and not the internet facing url. You can confirm this by plugging that value into an IFPS gateway[3]
The responses to that thread go into more detail, but I'll ask the more direct and pertinent question:
IPFS requires someone to pin the data - who will be doing that going forward? The platform? The artist? The owner? Thus far, it isn't anyone's responsibility to make sure the IPFS hash returns.
