You can learn more from a retard than a smartass.

Stand on the shoulders of shitposters.

Look hard for simplicity.

Live music: priceless Recorded music: $0.00000003 per stream

I am thinking about creating the concept of a “cpub” or child public key of a root npub. The idea is that the cpub can be provably traced back to a npub. I can have as many cpubs as I want, that map back to the same ‘identity’. If a cpub keypair gets compromised, I can publish an event that invalidates that cpub. As for clients, when they see what is a cpub, they can resolve back to the root npub and present that identity instead. The driving requirement is to have a protected root npub that corresponds to my identity; it is high-value so I only want to sign with it when absolutely necessary - keeping it on a hardware signer device. Any comments on this approach?

“One of the important lessons of Promise Theory is that semantics and intent are always subordinate to the dynamical possibilities of a situation. If something cannot actually be realized, it doesn’t help to intend it furiously. Water will not flow uphill, no matter what the intent. With these caveats, one can still try to spread new actionable intentions to a group by starting somewhere and waiting for the changes to equilibrate through the cooperative channels that are already there. The more we understand the underlying promises, the easier it should be to crack the code.”

“We’re outsourcing our agency. And in doing so, we’re creating a world where a small number of people who retain the ability to think independently will have unprecedented influence over those who don’t” View quoted note →

👀 View quoted note →

Notes and Other Spam Transmitted by Relays.