I do like the nblob encoding. but for the k:10063 events, I imagine clients would only use it if the URI or URL failed to load. so the censorship resistant part would only come into play if its been taken down
Needing a note is the biggest downside here though, since now you require two lookups. I like nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8's since the nblob is self contained and has all the info you need.
It’s so simple that it technically could be a spec outside nostr itself. blobs and stuff transmitted over relays? #blobstr?
Discussion
No replies yet.