A joke sign, but the point is made.

Schnorr, we hardly knew ye. RIP https://medium.com/asecuritysite-when-bob-met-alice/claus-peter-schnorr-rip-dab7d2944918

Invisible eSIM intermediaries https://aanjhan.com/assets/sec25-motallebighomi.pdf

Nothing new under the sun... What we are doing is associating names to records and signing them. The latest iteration of associating names to records and signing them is the #nostr protocol. But there is something new under the sun... You get to keep your keys (npubs) and choose your record managers (relays). It's a protocol that is resistant to authority capture.

We’ll get the interwebs back… View quoted note →

I’m @anon2722 if you happen to be within six feet of me. #bitchat

A npub is like a phone number. Nobody remembers your phone number. They don’t look it up in a phone book, they just put it in their contacts from their recents. Nostr won’t be any different.

trusted bots == military intelligence

HTTPS message signatures took 11 years to adopt, so we’re still good.

The Cloudflare Blog

Message Signatures are now part of our Verified Bots Program, simplifying bot authentication

Bots can start authenticating to Cloudflare using public key cryptography, preventing them from being spoofed and allowing origins to have confiden...

Message Signatures are now part of our Verified Bots Program, simplifying bot authentication

This is the best privacy policy. View quoted note →

'Safety' is just another word for more top-down control.

e-safety - it's a thing

Mobility & Transport - Road Safety

eSafety

eSafety

REST https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

I had ChatGPT summarize my research and thinking about message queues into a blog post. Please excuse the clippy tone, there is some useful info here: ⸻ Why Nostr Messaging Queues Are More Resistant Than REST APIs In the world of digital communication, REST APIs have long been the standard for client-server interactions. They’re predictable, easy to integrate, and widely supported. But they also come with structural vulnerabilities that make them brittle in adversarial or decentralized environments. Enter Nostr—a lightweight, censorship-resistant messaging protocol that’s quietly redefining how we think about message delivery and system resilience. While Nostr is typically seen as a social or publishing protocol, at its core it functions as a kind of message queue—and a remarkably resilient one at that. ⸻ 🌐 REST APIs: Centralized and Fragile REST APIs rely on a centralized request-response model. The client initiates communication by sending a request to a known server, which processes it and returns a response. This tightly coupled interaction assumes that the server is online, reachable, authorized, and responsive. In adversarial settings—such as environments with censorship, high latency, or denial-of-service attacks—these assumptions often fail. REST APIs become single points of failure and are easily blocked, rate-limited, or decommissioned. ⸻ ⚡ Nostr as a Decentralized Messaging Queue Nostr flips this model on its head by embracing a decentralized, publish-subscribe architecture. Clients send signed events to one or more relays. These relays, which are untrusted and easily replicated, store and forward events to any subscribing clients. This decouples the sender from the recipient and transforms the relay into a kind of stateless message queue. The result is a system where message persistence, delivery, and filtering can all occur independently of centralized control or even direct client-to-client awareness. Unlike REST APIs, which depend on a single endpoint, Nostr clients can broadcast messages to many relays simultaneously. Subscribers pull data based on their own filters, creating a robust, self-curated stream of relevant content. No single relay needs to be trusted or relied upon, and users can switch or self-host relays with minimal friction. The result is a system that offers inherent resistance to censorship, downtime, and infrastructure fragility. ⸻ 🔄 Nostr Wallet Connect: Evolving into a Resilient Message Queue Server One of the most promising evolutions of this architecture is Nostr Wallet Connect. Originally designed as a simple method for wallets and apps to communicate using Nostr events, it has increasingly taken on the characteristics of a resilient message queue server. Instead of relying on tightly integrated APIs, wallets can push and pull payment requests, invoices, and metadata using Nostr events routed through relays. These messages can be signed, broadcast, persisted, or retrieved later—making the system ideal for asynchronous financial messaging. In this role, Nostr Wallet Connect inherits the strengths of Nostr: decentralization, offline tolerance, cryptographic authenticity, and graceful degradation. It opens up the possibility of building a new class of wallet infrastructure where critical financial communication does not rely on any single API endpoint, service provider, or uptime guarantee. ⸻ 🛡️ Resistance by Design What makes Nostr fundamentally more resistant than REST APIs is that it doesn’t rely on a single communication path or authority. While REST APIs are tightly coupled and exposed at a known surface—making them ideal targets for censorship or throttling—Nostr clients can communicate with any number of relays, choosing freely from a global pool or self-hosting their own. Authentication in Nostr is cryptographic and embedded in the message itself, not granted by tokens or roles managed by a central server. Messages are not only signed and verifiable, but they can also be replayed or cached across multiple relays. This means that outages, censorship, and infrastructure decay have far less impact. ⸻ 🧪 Use Cases Beyond Social Media Although Nostr was born out of the decentralized social media movement, its underlying pub-sub mechanics make it suitable for a much broader range of use cases. Sensor networks can publish telemetry data to relays without relying on a central broker. Secure audit logs can be written once and replicated across multiple untrusted relays. Peer-to-peer communication, even across NATs or unreliable mobile networks, becomes feasible with store-and-forward relay logic. In each case, Nostr acts not just as a messaging layer, but as a resilient, programmable queue infrastructure for decentralized applications. ⸻ 💡 Conclusion Nostr isn’t just a protocol for social freedom—it’s a resilient backbone for communication in adversarial, distributed, or degraded environments. By functioning as a lightweight, stateless message queue, it offers a compelling alternative to REST APIs in systems where robustness, decoupling, and decentralization are strategic advantages. As tools like Nostr Wallet Connect mature, the ecosystem is evolving toward a future where even the most sensitive communications—financial transactions, identity negotiations, or supply chain signals—can flow through a network that refuses to be silenced, centralized, or shut down. In a world increasingly defined by systemic risk and contested control, Nostr’s design isn’t just clever—it’s essential.

Anybody going to this? https://www.blackhat.com/us-25/briefings/schedule/index.html#not-sealed-practical-attacks-on-nostr-a-decentralized-censorship-resistant-protocol-45726

#nostr #safebox working like a charm with Alby Go (Android and iOS), Damus, and of course, the web app. Payments work great; just wait until I get all of the decentralized record sharing working, too! Onward! 🥁

I agree with @jack

Very cool. I have #nostr #safebox now working with the #getalby client