Open Protocols

Guide tag · 51 matching pages

50 Nostr Questions

Fifty Nostr questions linked to guides on identities, relays, security, and use.

A public post is signed by a stable public key, so people can link its activity over time.

Privacy depends on the messaging scheme and client.

A relay can reject, remove, or decline to show events on its own server.

A different private key produces a different public identity under Nostr's basic key model.

You can publish a NIP-09 deletion request for your own event.

An ordinary signed event is immutable: changing its content changes its ID and requires a new signature.

Yes.

Some clients can connect to relays through Tor when configured to use a Tor proxy or a Tor-capable environment.

Yes.

No.

No.

Not necessarily.

Compare the full public key with a key the person has shared through a trusted channel.

Different clients, relays, and groups can make their own choices.

A Nostr follow list is itself a signed event, defined by NIP-02.

Keep a secure record of your private-key recovery material, plus your public key, chosen relays, and any client export of follows.

Start with relays your client can reach reliably, then consider their rules, retention, cost, location, and support for the NIPs you use.

Treat a public media URL as public unless the host provides real access controls or you encrypt the file before upload.

Choose a trustworthy Nostr client or signer and use its account-creation flow to generate a keypair.