I believe NIP-94 content in Kind1 is vital to the scalability of Nostr and must become a required feature for static content URLs in the future (Image/content server hacking is a real threat to the protocol when we scale up)
So, to help achieve that vision, I will turn NIP-94 content optional for now (two buttons: regular URL or hashed/accessible URL; user's choice) if nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s agrees to implement a simple NIP-94 viewer, as the spec is today, in Damus (no need to create NIP-94 events).
What do you say, nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ?
I can see why the implementation of NIP-94 is important.
I am now copy-pasting the URL from xyz.com, which is a cute cat picture.
What if, tomorrow someone else captures rights to xyz.com tomorrow and starts serving an objectionable pic from the same URL as the earlier cute cat picture?
NIP-94 protects us from the misrepresentation of our content by people with loads of cash and power.
No replies yet.
