#[4]ā is replacing urls with notes that you have to fetch to get the url which adds extra latency to image loading. I would rather just have this info in the kind1 tags so I donāt have to n+x notes for every note in the timeline.
Discussion
The extra metadata is great and I will likely do something similar, but I probably wonāt have it in a separate note.
Makes sense, thanks for explaining! š
Guys, I was watching the entire conversation with šæ
was here by accident , do not regret it
š coding reality show
Absolutely. I find it funny that the thread starts we me posting « Iām tiredā¦Ā Ā» then they barged in.
«Jb comes from the right to aggressively tackle the issue »
« Vitor Pamplonaā attempts to deflect the attack. It looks as if maybeā¦Ā Ā»
« But Jb doesnāt give up and tries again from the leftĀ Ā»
« Vitor Pamplonaā seems to have found a way to maybe divert the flow of the action in the other directionĀ Ā»
« no, What a shocker pablof7zā enters the ring unexpectedly tapped in by jb55 
šššš
LOL
That sums it up! š
Oh and by the way, I had to go back to an older version of Amethyst because I want to be able to upload images that everyone can see directly in my client.
So tell me if you can see the image that started it all! š

how to add two image with NIP-94?
Iām not entirely sure. My guess would be that in the kind=1 note content, youād have # [0] and # [1]. Then in the tags, youād have two āeā tags pointing to two different kind=1063 (NIP-94) events.
I still support kind 1 event with urls in content.
and NIP-94 event will also showed but don't be send from my client.