But this note got blocked by the Damus relay again. It definitely looks like intermittent rate limiting 👇🏻 View quoted note →

What's new in Quill, the text-first Nostr client that tells you why it hides things: • Quoted notes show inside the note that quotes them, judged by the filter like any other. • Pictures and videos: a "Show image · site" button loads them straight from their site, only when you tap. Quill keeps no copy. Optionally, pictures from people you follow load by themselves. • A Popular feed: notes by anyone that the people you follow reacted to or reposted in the last day, each saying who. • Search: instant, on your device, in what Quill has loaded; a hashtag also asks your relays; a button asks two search relays only if you want. • Mute from an account page or a note's menu, with the same care as following: one account changes, the rest of your list (private part included) stays. • Each account page shows how much the network vouches for it, with the reason for every point. • A light theme.

Quill

Has anyone else seen relay.damus.io turn notes away lately? Twice in two days, publishing a single note from my own key, damus first answered HTTP 503, and a retry a few seconds later got "rate-limited: you are noting too much". The same signed note was accepted by the other five relays I publish to. I don't post much. Not a complaint, damus carries a huge load. Just curious whether it is a new limit, something about my key, or a bad moment. #nostr #relays

Heads-up for anyone using relay.nostr.net: today it refused most connections from my side (HTTP 500 on 4 of 5 attempts; the relay info page itself answers fine), so my notes kept landing on 5 of 6 relays. I swapped it for relay.damus.io in Quill's defaults and in my own relay list. relay.snort.social was the fastest I tried, but it only keeps events in memory; nostr.bitcoiner.social and offchain.pub reject events from keys outside their web of trust. If you run it and want details, happy to share what I saw. #nostr #relays

The bunker connection with Clave worked fine until this afternoon. From then on it started giving me various types of connection problems, I guess because of iOS. So in the end I had no choice but to create my own bunker hosted on a VPS. View quoted note →

Why I built my own Nostr signer My phone signer kept failing when I needed it. iOS suspends apps, its background wake-ups were unreliable for me, and after I deleted one connection I could not pair it again. Quill, my relay's admin panel and my MCP assistant all stopped signing in the same day. So I wrote hivescope-bunker, a NIP-46 remote signer for one account that runs on my own server: • The key is encrypted on disk (NIP-49) and the bunker starts locked: I unlock it by hand after a restart • Each app has its own connection that can sign only the kinds of event it needs, with an hourly limit • The relay panel's connection signs only logins for its own address • No open ports: it only connects out to relays The trade-off is real: my key now lives, encrypted, on a server instead of in a phone keychain. Open source, MIT, written in Go:

GitHub

GitHub - rzazo24/hivescope-bunker: Self-hosted NIP-46 remote signer for one Nostr account. Key encrypted on disk, unlocked by hand, and a separate connection per app that signs only the kinds it needs.

Self-hosted NIP-46 remote signer for one Nostr account. Key encrypted on disk, unlocked by hand, and a separate connection per app that signs only ...

#nostr #nip46

Quill: a small, text-only Nostr client that tells you why it hides things. • Nothing external is loaded: no images, video or link previews. The browser enforces it, not just the code. • A filter you can read: every hidden note says which rule hid it and what the rule saw. One tap shows it. • You write through your signer (Clave): Quill never sees your private key. • Replies, reactions, reposts, a Network view (the people your follows follow), notifications inside the app. Installs as a phone app, no backend.

Quill

Open source (MIT):

GitHub

GitHub - rzazo24/quill: Small text-first Nostr client that tells you why it hides things. Explained spam filter with web of trust, zaps through your own wallet (NWC), pictures off unless you choose, no backend, signs with any NIP-46 remote signer, installable PWA.

Small text-first Nostr client that tells you why it hides things. Explained spam filter with web of trust, zaps through your own wallet (NWC), pict...

#nostr #quill

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 @npub1clav...539g 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.