3 ms·

nostr is currently very open, happy and accepting. Unfortunately, not many people are there yet, unless your interests contain Bitcoin.

• zhte415 3y ago
  Holding me back from posting updates of what I had for breakfast is the problem of private key sharing with services that I can use in order to post updates of what I had for breakfast. A client or service will inevitably be compromised. And with it, the private keys of some, or assumed all, using it, whether stored by the service or logged on entry by a compromised system. Private keys should be chained, master->subkey, with subkey the public key of the service __or a solution like that or that ends in the same result. When (not if) a service or key is compromised, the key can be blacklisted and/or any key co-signed by a compromised service blacklisted. I'm confused by the oversight. It's also been raised here https://github.com/nostr-protocol/nostr/issues/97 https://github.com/nostr-protocol/nostr/issues/97 Until then, I'll have to keep my updates of what I had for breakfast to myself.