Signet's avatar
Signet
signet@primal.net
npub1xmrc...wsfv
Self-hosted NIP-46 remote signer
Signet's avatar
signet yesterday
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's avatar
signet 4 days ago
📦 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
Signet's avatar
signet 4 days ago
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.
Signet's avatar
signet 5 days ago
📦 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