How far away are we from "self-healing" blossom links?
Discussion
In the best case I want my haven relay to continually grab everything I'm interacting with, including media, and mirror it on my own blossom server.
And in the very best case no links ever break ever, but I guess that's impractical right now as we rely on https instead of blossom://
Wow
The 'innitial' link is there for convenience, and there is no reason to not have it;
Other than that perhaps it creates lazyness in terms of implementing what ought to be implemented
That's akin to saying that all notes should be linked like this: https://primal.net/e/note189n0l9cy52rzxj35k0up8nppehv9s2exva5r9qdtlxa7aagkfemqay88sm
No, that is a crime, only exceeded in severity by screenshots
I'm glad we're on the same page https://primal.net/e/note1xf6gzzuhf5zeag0gwfwldehlx8hhcgd3n6qj7x28cljup379qldsupta76 
There's a couple reasons to have it: simplicity and backwards compatibility.
If its not a URL clients MUST support blossom, increasing the barrier to entry.
Fair enough, but you could make the same argument for nostr:noteid links. Imho we should still think about how to potentially get there step by step, no?
What is the argument, im confused.
Are you refering to note vs nevent?
Or nostr:nevent vs https:njump ?
Because if it is the latter, i did not even bother to respond the first time, but non of the nostr clients understand https: references as a reference to a note, just as a reference to a webpage, that contains that note.
Whereas all the clients do understand a https://......mp3/webm/mp4/jpg and render it.
So id say no, the same argument cant be made. It would have been true if all the clients understood https://...nevent but nostr:nevent would have been some new thing that was introduced later
Yes, that's what I'm referring to.
Some clients understood https first and nostr later, and some clients do replace https URLs and render the note properly.
Primal, at least on Android, will render the following as if it were a nostr/nevent link (even though it's https dot primal net)
https://primal.net/e/note1yv7meallmrsjreaqgtula2uvq5kfakltz893f4y4as9n6zfv359q4kx4gx
Your question has prompted me to create nostr:npub14sl07pu8rq2e3c9gz2qm3087gxn4panhmy0lsv8qtncgcuh0urrs2tpscu
We can use it to test nostr clients.
- I had success with "host not found" failover in Nostrudel and Primal.
- Removed blobs (404) did not fail over.
👀
I thought the idea with blossom would be to have a link that fallsback to an available server. That way I could eternalize my media. Now what I currently have is a direct URL to my personal blossom server, and if that's offline, I get a broken link.