I guess at least if you keep a copy of your NFT you can start serving it over IPFS yourself if whoever is hosting it can't be bothered anymore, or pay a service to on your behalf. It's sort of the ideal use-case for content-based addressing, I would think, since you're trying to prove some sort of connection with/ownership of/patronage over a piece of content. And it should be more long term resilient than a centralized solution as long as the NFT owners themselves don't lose their own files. At least the incentives are aligned (if you own the NFT you will want to keep at least one copy, if only so you can show it to potential buyers!)
It seems a substantially less silly idea than pointing a token at a url that you don't control. I guess I'm surprised that NFTs aren't all hosted on IPFS or something like it, if only as a backup. Like, have these people not heard of linkrot?
But I guess as long as the buyers don't realize yet that their immutable ledger entry can become a dangling pointer in a puff of smoke, it doesn't matter.
> But I guess as long as the buyers don't realize yet that their immutable ledger entry can become a dangling pointer in a puff of smoke, it doesn't matter.
I was surprised too, but only for a moment. In the end it's basically just a record that you "own" a small amount of data (url, ipfs hash, 'coin'). Unless my ownership gets me some utility (like exclusive access to the jpeg, maybe? Ability to transfer the ownership to El Salvadorian govt to pay my taxes?), I don't see how it has value
It seems a substantially less silly idea than pointing a token at a url that you don't control. I guess I'm surprised that NFTs aren't all hosted on IPFS or something like it, if only as a backup. Like, have these people not heard of linkrot?
But I guess as long as the buyers don't realize yet that their immutable ledger entry can become a dangling pointer in a puff of smoke, it doesn't matter.