More of this, every kind should compose with every other kind
I just zapped nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 's zap
nostr:note1c0wj73u4qk45tukls77fayqp3cgc7wrc5gvfx89jw0eyvwwfyc9qp6c0mu
Discussion
Exactly.
This is a super power of nostr and clients shouldn’t hide this feature.
It does present interesting and novel UX opportunities that we’re barely beginning to explore.
Render libraries would be helpful here.
On the other hand, nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpz3mhxue69uhhyetvv9ujumn0wd68ytnzvuqjyamnwvaz7tmwdaehgu3dwejhy6txd9jkgtnhv4kxcmmjv3jhytnwv46qz9thwden5te0dehhxarj9ekkjmr0w5hxcmmvqyvhwumn8ghj7mn0wd68ytn6v43x2er9v5hxxmr0w4jqz9thwden5te0v4jx2m3wdehhxarj9ekxzmnyqyxhwumn8ghj7mn0wvhxcmmvfdjas6 pointed out on github that composability hurts interoperability. What do you think of that idea?
Where did he say that? Would love to know the rationale
The rationale is behind a paywall.
Context is basically the same, re-posting non-kind 1's
https://github.com/nostr-protocol/nips/pull/576#issuecomment-1593932338