No, that’s not it. The hashing is about making the content addressable, which means that the *where* the data, the media, comes from, is non-important.

Ok, that gives us the same thing relays give us on nostr, so what?

The next piece of the puzzle is the pubkey, tying a blob’s hash to a pubkey allows you to easily retrieve the list of blossom servers  that pubkey uses; so when you have a url from a pubkey pointing to server1 as the place to find file with hash1

When server1goes down/censors, you can ask nostr in the same way we use outbox model to find which is the new server for that same pubkey

You now have a list of candidates servers that pubkey moved to and a hash; you can just ask for the hash to those servers and voila, maybe you’ll get your file.

Since you also can talk about this blob by its hash you can use other tricks to find it or DVMs to go and do the searching for you in exchange for some sats.

It really is extremely simple but it works and it’s super powerful.