It's a way to incentivize the use of zaps View quoted note →

Your relay list is how people find your notes. Many clients read it (NIP-65) to know where to look for your posts, so it should match where you actually publish. I just tidied mine: it now lists the same six relays I publish to, and I removed a private address that nobody else can reach, so their clients no longer waste time trying it. Worth a look at yours. #nostr

Hey @⚡️ᗪㄖ匚⚡️. I'm using @Clave as a signer in an MCP project with Claude. I use it in low trust: get_public_key does it in the background but when I try to sign a kind1 event Claude sends the request but Clave doesn't receive it. It happens to me when I use Termius (iOS app) to connect via SSH to my VPS. From PC it works fine.

One signature, four relays. I sign a note once and the same event goes to all four, but each relay answers on its own. The first time I tried it, two of the four refused: one returned a 503, the other never answered. Checking afterwards showed exactly where the note had landed. "Sent" does not mean "stored". Ask each relay. #nostr

On Nostr, deleting a note is a request, not an order. I asked four relays to delete a test note of mine, then asked each one again: all four had dropped it. That only proves what those four relays do. Any relay or client that copied it earlier may still have it. Check, don't assume. #nostr

Not every bot is spam. Reading the replies to my notes this week I found two very different kinds: 🤖 one answered 60 different strangers with the same advert and a link, over 100 times 🤖 another posted 150 events in a single minute, yet only its own reports and reactions, never an advert aimed at anyone On volume alone they look the same. What gives the first one away is what it says to other people, not how often it posts. #nostr

nostrclaw 0.9 🦞 — what's new in the MCP server for analysing Nostr relays and publishing with Clave: 🕵️ review_interactions: who replies or reacts to a note and whether they look like a bot (it tells an advertising bot from one that is merely automated) 🩺 doctor: checks the set-up and tells you how to fix whatever is wrong 🌐 analysis across several relays at once ✍️ replies and reactions with correctly built tags, and a check that Clave is awake before asking for a signature Open source:

GitHub

GitHub - rzazo24/nostrclaw: MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation.

MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation. - rz...

#nostr

Testing nostrclaw 0.6.0: it now checks that Clave is awake before asking me to confirm a signature. 🦞

Testing nostrclaw: Claude Code on my computer, signing in Clave on my iPhone. 🦞

Meet nostrclaw 🦞: an MCP server (TypeScript) that lets Claude analyse a Nostr relay and, if you want, publish on your behalf. 📊 Read-only by default: relay info, activity, suspicious keys, a trust score based on the follow graph, relay-to-relay comparison… ✍️ To publish it signs with NIP-46 (I use it with Clave on my iPhone): your private key never leaves the signer, and every note needs your confirmation and your approval. Anything coming from third parties is treated as data, never as instructions. Open source:

GitHub

GitHub - rzazo24/nostrclaw: MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation.

MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation. - rz...

#nostr #mcp

“Broadcast to other relays” in @Nostr Vault is top👌🏻

Os presento nostrclaw 🦞: un servidor MCP (TypeScript) para que Claude pueda analizar un relé de Nostr y, si quieres, publicar por ti. 📊 Por defecto solo lee: información del relé, actividad, claves sospechosas, puntuación de confianza según la red de seguidos, comparación entre relés… ✍️ Para publicar firma con NIP-46 (yo lo uso con Clave en el iPhone): tu clave privada nunca sale del firmador y cada nota pide tu confirmación y tu aprobación. Todo lo que viene de terceros se trata como datos, nunca como instrucciones. Código abierto:

GitHub

GitHub - rzazo24/nostrclaw: MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation.

MCP server that lets Claude analyse a Nostr relay (read-only) and, optionally, publish through a NIP-46 remote signer with human confirmation. - rz...

#nostr #mcp

Segunda prueba de nostrclaw: ahora en nostr.mom y relay.nostr.net. 🦞

Probando nostrclaw: publico a la vez en cuatro relés. 🦞

For those who like to know what's happening in the world, I've designed this app that, based on data from GDACS (Global Disaster Awareness and Coordination System), reports all events through its API. It also reports earthquakes in Spain through information from the Spanish IGN and the European EMSC.

Disaster Watch — Alertas globales GDACS

Mapa en tiempo (casi) real de alertas globales de catástrofes —terremotos, ciclones, inundaciones, volcanes, incendios y sequías— con datos p...