ah, i don’t think i was clear that it created a mapping from npub to the blob. that does help a lot, thanks for clarifying.
fwiw, this discussion came up in private as i was working with a friend on exploring Highlighter’s long form blogging tool. looks like media is currently uploaded to nostr.build. is Blossom ready for a service like Highlighter to use or still need more development first?
No, it's ready for prime time; I'm working right now on replacing nostr.build with Blossom endpoints-only.
It will default to Primal's blossom server but it will be easily configurable.
In fact, this very screenshot was uploaded from Highlighter to the Satellite blossom instance, and if it were to go down, it would automagically heal.
“Automagically” is the best word I’ve heard all year
👀
Okay, let me get this straight.
So this image is from a blossom server, but it is linked to directly from a webserver (cdn.satellite.com)
So for this to automagically heal, you have to configure known blossom servers on your client so that it will identify missing images from a blossom server and redirect to other blossom servers in order to find the image?
I didn’t know it mapped to an npub either. That’s super cool.
It’s npubs all the way down lol… and that’s probably a good thing.
I’ve heard nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg noting about npubs to address cashu mints
I was talking with someone recently about npubs to be website addresses and I think nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft shared something like this today?
and now we’re learning from nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr that Blossom addresses a piece of media with an npub where the underlying serving location can be re-mapped making the media serving more resilient
maybe npubs are really about creating an abstraction/mapping layer when accessing any entity, be it person or service?
Yup. 100%. The addressability plus the layers of “how to find stuff related to me” that the protocol already does makes it like the universal join table for nostr data.
I’ve been digging in on double ratchets and syncing big groups across devices and, wouldn’t you know, I think npubs are going to solve problems there.
