CodeMichael

Hugo and Mkdocs are both frameworks you should take a look at for building websites with markdown.

e2e means you don't have to worry about transparent 3rd parties keeping secrets for you. It prevents casual abuses of your privacy and sets the bar for violating it (deserved or not)

If size is your only criteria then you might be right, but look at the company policies on privacy. Cloudflare has some pretty specific customer-oriented privacy policies. Comcast's policies are specifically set up to sell you and your information. That's a meaningful distinction and one with some (not much, but some) legal weight in the US.

I'd recommend limiting it to two by default: the keybase icon, and the site icon.

Does that assume that all of the components (browser and server) support 1.2 as well? In a theoretical future state if I disable 1.2 on my browser doesn't that mean I won't trust a MITM box.

If I'm not mistaken this means no "authorized" MITM

  - Static RSA and Diffie-Hellman cipher suites have been removed; all public-key based key exchange mechanisms now provide forward secrecy.

+1 -- I would really like files to be working at all, but integration with iOS11 files feature would be amazing (also would love to see iPad working)

Correct, last article I recall reading about deciphering VBR from packet size alone was something in the neighborhood of 50% success rate.

Sounds like marketing speech for variable bitrate encoding and/or adjusting compression aggressiveness.

Worth noting that the watch alerts that it has been used to unlock the laptop. Doesn't prevent the action, but does prevent "stealth mode unlock"

Agreed, logged history and in-transit communication should not be considered the same thing.

If anyone is still looking I have quite a few sitting idle.

Nice! Thanks for contributing that feedback and helping to get movement on it.

Unless you're in the habit of cleaning your phone after every single use your fingerprints are already on the device. Case 2 has different dimensions than what is stated.

Thanks for the response. My sense from the information is that the protocols are extremely similar, the implementation is the primary difference.

I'm trying to find more info about https://wire.com

They would seem to be doing all the right things, such as OTR and not rolling their own protocols, but I've only been able to find a couple of opinions and nothing concrete.

The fact that they've made effort to open source it and are letting people write their own clients for it is encouraging, but not proof that it's a solid system.