Spam is a challenge for Nostr. Anyone can create a keypair and anyone can post. Low barrier to entry means spammers can create endless accounts.
Defenses exist. Proof of work raises the cost of bulk posting. Paid relays filter out casual spam. Web of trust can prioritize content from people your follows follow. Clients can implement spam filters, with some hiding posts from accounts with no followers and some using reputation systems.
No solution is perfect, and spam is an ongoing arms race. But the decentralized architecture means different relays can try different approaches, and what works will spread. Your personal defense: mute aggressively and use relays with good policies.
Signet
signet@primal.net
npub1xmrc...wsfv
Self-hosted NIP-46 remote signer
📦 Signet commit
Brought web UI and Android app UI closer in line. Fixed approval/denial bug in Recents widget. Additional UI tweaks and bug fixes.
e32d1c8

GitHub
Brought web UI and Android app UI closer in line. Fixed approval/deni… · Letdown2491/signet@e32d1c8
…al bug in Recents widget. Additional UI tweaks and bug fixes.
📦 Signet commit
Fixed an issue that prevented the Android app from detecting version number.
ee0b3d1

GitHub
Fixed an issue that prevented the Android app from detecting version … · Letdown2491/signet@ee0b3d1
…number.
📦 Signet commit
Update http-proxy to fix DoS CVE, added QR codes to each IP the daemon detects for easier Android app setup, labeled Tailscale IPs as such for differentiation, updated build scripts and Dockerfiles to eliminate build warnings and daemon inconsistencies.
6693383

GitHub
Update http-proxy to fix DoS CVE, added QR codes to each IP the daemo… · Letdown2491/signet@6693383
…n detects for easier Android app setup, labeled Tailscale IPs as such for differentiation, updated build scripts and Dockerfiles to eliminate bu...
Nostr Connect is another term for NIP-46 remote signing. You might see "Connect with Nostr" buttons on apps, and this usually means NIP-46. The app wants to connect to your signer.
The flow is to scan a QR code or paste a bunker URL, approve the connection, and the app now uses your signer for signatures. Different implementations have quirks, with some using nostr+walletconnect:// URIs and some using bunker://. The underlying protocol is the same.
If something calls itself "Nostr Connect," it's probably NIP-46 compatible. Check the docs if you're unsure. With Signet, you should be able to connect.
Android app has been updated to version 1.1.1

Zapstore
Signet — Zapstore
Keep your Nostr private keys secure on a server you control. When apps need to sign events, Signet handles the request. Features: Real-time push no...
📦 Signet commit
Added QR code to daemon for non-Docker instances which can be scanned via the Android app to set up a new server. Additionally, fixed several compilation issues that could cause issues when running signet-ui via pnpm.
7a0cf23

GitHub
Added QR code to daemon for non-Docker instances which can be scanned… · Letdown2491/signet@7a0cf23
… via the Android app to set up a new server. Additionally, fixed several compilation issues that could cause issues when running signet-ui via p...