What is even more important imho is compatibility between clients. Not just standards but actually having no breaking changes and the same experience on a variety of clients
But I think NIP-94 will get adopted soon enough
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 ?
Discussion
No replies yet.