In basic ipfs the address is content-dependent hash - same url should always return same content (excepting hash collisions which should be so rare and improbab

In basic ipfs the address is content-dependent hash - same url should always return same content (excepting hash collisions which should be so rare and improbable as to never occur in practice). So the short answer is that there's nothing to update: and url will return the same content (or no content if no one has it pinned anymore). AFAIK the ipfs approach to this conundrum is a name/resolver system - which essentially adds indirection. This is Thomas he'll always be Thomas. But for now, he's also class valedictorian. Some time in the future, Thomas will still be Thomas, but someone else might be class valedictorian.