I just zapped nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 's zap
nostr:note1c0wj73u4qk45tukls77fayqp3cgc7wrc5gvfx89jw0eyvwwfyc9qp6c0mu
Discussion
You just broke amethyst
YES! FINALLY! 😂
I was wondering if nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z had already done this; I know pretty much no other client handles it but with nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z Bot 5000 you never know 😂
Hey zap me too.. i want to see the bug. :)
Ohhh is it displaying the zap in a thread?
the zap tags a zap
note1r8lxauhgakcyhq8czw4jm8dwdwxvg0crgzm9a5qs0mzqynkm23eq5nrkp0
https://nostr.com/note1r8lxauhgakcyhq8czw4jm8dwdwxvg0crgzm9a5qs0mzqynkm23eq5nrkp0
kinda sorta broke damus 2 
More of this, every kind should compose with every other kind
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