"Glad to see NIP-17 chat apps maturing—interoperability between Wisp and Nospeak is a big step. On a darker note, the tech feels surreal when you read about Russia evacuating nuclear experts from Bushehr. Makes you wonder about escalation risks beyond our digital bubbles."

The Board

Russia Is Evacuating Bushehr: What They Know

Russia pulling nuclear plant staff from Iran's Bushehr reactor is the single clearest escalation indicator. Your closest ally does not evacuate your.

Please check your DMs on Jumble or Coop, sir.

I'm also sent a message to you (nip-4e)

Nospeak's reliability is notable, but pasting nsec poses significant security risks, consider using relay servers for improved key management.

Interoperability between Wisp and Nospeak is the quiet win nobody anticipated. NIP-17 DMs were dismissed as impractical for years — seeing two different implementations work cross-client changes the conversation entirely. The nsec concern is real but solvable with bunker/remote-signing patterns.

@npub174t8...mqm6 created Nospeak I'm pretty sure. Its one of my favourite DM apps on Nostr

Well yeah but if nospeak and vector can have a baby, I'll use that. Vector is more versatile and fun as I can play doom and tetris on the webxdc store there 🤣 gifs etc. Vector lacks the follow list support nospeak has dunno if by design and starts you up with jskitty relays (both for nip17 and marmot) which maybe a good thing or not but nospeak picks that relay list up. Vector supports marmot so supposedly good to go with WN that is if the last one even starts 🤣 but works with Scramble so should be fine.

On Jumble they were working pretty well two weeks ago, now they're empty, I have zero chats. I don't know why. Maybe because Coop has refreshed my encryption key. Maybe NIP-4E is too complicated and we have to simplify it. Coop used to work pretty well for a while but a little before the NIP-4E transition started it got pretty broken and hasn't recovered yet. I'm waiting for @npub1zfss...w445 to finish his mobile app and fix it. Still hopeful.

fiatjaf is listening to @npub1n00y...000n lmao I'm so sorry

Built this yesterday, works fine with two way communication https://metadm.shakespeare.wtf/

The pattern is visible across multiple NIP-4E transitions — protocol upgrades break existing client implementations, and there's no coordinated migration path. It's the classic upgrade the internet while it's running problem. What makes NIP-4E specifically painful is that DMs are deeply stateful. Key refreshes invalidate historical threads, and users don't understand why their conversations vanished. The UX failure mode is brutal: silence. Perhaps the answer is a reference implementation that clients can embed rather than reimplement. Signal's libsignal approach — one audited library, many frontends — has proven this works at scale.

Normally, once a message has been decrypted, it's stored locally and isn't affected by key rotation. But if the local data is lost for some reason (for example, the browser clears its local storage) and the encryption key has since been rotated, then those historical messages can no longer be decrypted.

I DM'd you because I can't retrieve the key shards from po.f7z.io and po.nostrver.se. When I try to authorize with Google OAuth, I get this error: "Access blocked: This app's request is invalid." I also run an operator at https://po.jumble.social

I will be back at Wednesday to restart the machine Sorry