Thoughts?:
Specify preferred blossom server in profile metadata
Embedded links in notes are just the hash (no url)
Dynamically render media based on preferred server + hash
This way your old notes don't break when you switch servers
Thoughts?:
Specify preferred blossom server in profile metadata
Embedded links in notes are just the hash (no url)
Dynamically render media based on preferred server + hash
This way your old notes don't break when you switch servers
Yes. I was looking at IPFS before learning about blossom servers … for … this … exact … reason.
If the content is nearly immutable we need content that preserves regardless of the url.
Sounds like IPFS to me. I like this approach.
Just seen this (been out of Nostr for a while)... Something like this should already been happening (the part about querying servers from a nostr kind and falling back to whatever server implements its). The problem is that most clients haven't fully implemented Blossom. I think that linking the image directly to a URL is a good measure given that I dont expect clients to fully support blossom soon, and most clients will render a URL correctly. So my take on it is, keep Blossom links as is and annoy client devs to implement proper retrieval / fallback according to BUD-03.