nostr:npub10qdp2fc9ta6vraczxrcs8prqnv69fru2k6s2dj48gqjcylulmtjsg9arpj nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 shakespeare (with mkstack) was hesitant to integrate zaps. first it had "simulated zaps", then i cajoled it and it added a demo/live toggle but the "live" zaps were webln only, now i'm asking it for scannable QR invoices and it looks like it's building them from scratch with qrcode npm packages... is this normal? I would expect it to have zap integrations just as seamlessly as the other nostr features.