Nostr Web Client

I’ve documented the inline image metadata NIP in the new damus DIPs repo. The purpose of this repo is to document nostr specifications that damus implements that didn't quite reach agreement amoung other nostr client devs. These will always be backwards compatible changes that can be safely ignored by other clients (optimizations, etc).

https://github.com/damus-io/dips

s3x_jay 2y ago

One suggestion…

Nostr doesn't really have the idea of srcset like figure>img does in HTML. AFAIK NIP-94 doesn't really have the ability to do it either because it's one hash per event and each size of an image would have a separate hash.

But what you're doing could be modified to support the idea of srcset - so it lists all the sizes available and then the client would pic the one that's appropriate for the UI at the in the moment. It could reduce bandwidth usage by the client when multiple sizes are available.

Reply to this note

Please Login to reply.

Discussion

Heri Sim 2y ago

Keep the good ideas flowing.

jb55 2y ago

Hmm yeah maybe once uploads are smarter and could generate multiple variations

s3x_jay 2y ago

Guess what I’m saying is you might want to future-proof your spec so it won’t be disruptive when it happens. Right now you’re mixing things that apply to all sizes (the sky tag) with things that apply to a single size (dims, hash).