Oddbean new post about | logout
▲ ▼
doot | 3 months ago (raw) | root | parent | reply | flag 
 i think blossom is overall a much better approach to media on nostr, so id rather support it
▲ ▼
melvincarvalho | 3 months ago (raw) | root | parent | reply | flag 
 not really a lot of difference, nip-98 is superior, scales better, can do more -- but it's nice to have more than one way of doing things

we are all still learning -- most of this will get replaced in next generations, in any case.
▲ ▼
doot | 3 months ago (raw) | root | parent | reply | flag +1 
 one of the things i like about blossom is that it standardises CDN on nostr, while staying very simply. it end’s up being very much like how we interact with relays.  

in the future, i can also see how it would help us keep media in notes tamper-resistant.
▲ ▼
melvincarvalho | 3 months ago (raw) | root | parent | reply | flag +1 
 This use case was always possible, and has already been standardized at the ietf in RFC 6920 for a decade.  Blossom doesnt really standarize it, imho.  It proposes an api which pollutes the namespace, and wont fly in certain deployment scenarios.  But it is a system that works, and could perhaps be future-proofed with the use of reverse proxies.  I wouldnt get too wedded to the system tho.  There is sufficient technical debt that further iterations will be needed, imho.