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).
Discussion
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.
Keep the good ideas flowing.
Hmm yeah maybe once uploads are smarter and could generate multiple variations
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).
I learned early on that people in git issues don't control the Fediverse, developers do. It's the same with Nostr.
Add inline image DIP reference to the long from note feature request
Is there a possibility to use the key as something similar to a phone nr. in the future so theres no need for relying on diff carriers.
I know at the moment theres still reliance on wifi/inet connection but then again im still hoping there’ll be a solution to have access to wifi through a diff source then phone carriers that aren’t secured enough or being tapped by gvnments.
The free porn that those agents listening in mustve gotten out of it.. 🥴😵💫🤐😬