@cwebber I prefer a mix to be honest. It's nice to be able to publish stuff where at least the message text is not provable to third parties sometimes. Still wish we had TLS client certs instead of HTTP signatures (draft version :blobfoxmeltsob:) for Authorized Fetch [since as a signature over a symmetric encryption key, that lets the recipient trivially forge any payload as long as there's no proxying (client-aware) notary similar to https://tlsnotary.org].

I'm aware it's at the cost of availability though. (I think we can discard the idea of slapping an "untrusted" badge on posts and expecting people to not think it's real anyway.)