None of my one-hop trusted people are part of the cancelmob. If I found that somebody two hops away from me did something absurd it's quite easy to do something about it -- apply negative trust to whatever path endorsed that nonsense.

Unfortunately people these days seem allergic to running anything that isn't a web browser or served by an app store, and the entities that control those two channels are extremely unexcited about decentralization.

Wikipedia helpfully selected a picture of somebody using an ebook reader as their illustration of what "screen time" means: https://en.wikipedia.org/wiki/Screen_time

I'm just flabbergasted with the level of smokescreen that goes on in this discussion. Pretty sure reading books on ebook readers is not what is driving teenage mental health problems.

They pinky-swear.

https://github.com/MichaelMure/git-bug/issues/749#issuecomme...

They really don't want you to leave their walled garden.

A DID is a public key. If you don't know the corresponding private key you won't be able to make any updates. All you'll be able to do is mirror it.

instead just get more nodes to follow them than the original

This is like saying "but I can fork Verisign's Root CA certificate and get more nodes to follow me than Verisign!". No, you don't have the private key that goes with that root certificate. So everybody will ignore you.

Cryptography is not a popularity contest.

Suburbs, for better or for worse, have been around for a long time. They cannot explain the massive decline in Generation Z's mental health compared to its predecessors.

PS, next time try to link to housing costs -- that one gets better karma yield. Bonus points if you can somehow denigrate cryptocurrencies while you're at it.

There's a whole book about this, called Rainbows End. Highly recommended.

War, unfortunately.

Exchanges above the dotted line are one-time key distributions; see this link: https://archive.li/bU5Me#selection-3667.0-3671.36

I'm not sure what attacks you refer to when you say "malicious program-binaries". I'm having trouble imagining something fitting this description which is thwarted by the vendor blowing the programming fuse but isn't thwarted by you blowing the fuse yourself.

Apparently some people haven't heard about Stacker News (okay it's more like $0.0001 per post, but anyways...)

Then you not only have access to the device secret, you can even choose it yourself.

https://noiseprotocol.org/noise.html#interactive-handshake-p...

I encourage you to use their hashing details. They're battle-tested.

Wireguard uses Noise IK, which is NK plus a static public key for the initiator which is encrypted to the agreed-upon-session-key without adding additional round trips. Your protocol and Noise NK omit the parts related to the initiator's static public key, because it has none.