I enabled zap receipts from pubkeys outside your social graph (like many zap receipt issuers are) and now most zaps are visible again on iris.to. I'm terrified of the possibility of fake zap receipts, but for some reason no one has spammed them yet 😄 Maybe at least nip05 should be checked for zap receipt issuers, although that's not a long term solution.

iris.to replies and quotes might be targeting correctly now, finally

@brugeman can we get brotli / gzip to nostr.band apis? 🙏

@calle thinking about how to best do Cashu zapping in iris.to. Maybe keep Cashu open in the bg in iframe, nostr wallet connect to it, but send events over postMessage channel (in addition to relays?)

Aika hyvä / ganska bra

Social graph filtering reduces new user visibility, but at least you don't see reply bots on iris.to

Mid-answer, Cursor started spitting out a 10-page Kubernetes config in Chinese, with username and all. LLM glitch or Cursor security issue?

post custom emojis for testing

Double ratchet tests passing in my Damus fork. Yet to properly hook it into Damus UI and event system.

GitHub

damus/damus/Models/DoubleRatchet at doubleratchet · mmalmi/damus

iOS nostr client. Contribute to mmalmi/damus development by creating an account on GitHub.

Double ratchet NIP — Signal style DM encryption on Nostr. Deployed on https://iris.to View article → Double ratchet invites: View article → Github PR

GitHub

Nostr Double Ratchet by mmalmi · Pull Request #1813 · nostr-protocol/nips

Implementations: nostr-double-ratchet typescript library, deployed at iris.to

Kek, I didn't know how Nostr works and used 30078, without "d" tag, and wondered why my double ratchet DM events were not properly stored or relayed. Works much better now with kind 1060.