#[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.

Reply to this note

Please Login to reply.

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! šŸ˜‰

Yes

Interesting…

🤣🤣🤣 if that cat knew what he had started

šŸ”„šŸ™€šŸ”„

Right? We started such an amazing debate! šŸ˜‰

I’m glad I caught a glimpse of real dev behavior in the wild. It wasn’t this exciting when I saw them at the zoo… I meant the office

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.