allen-chen

2 ms·

1. 1.▲
   by allen-chen 10mo ago

   Makes senses — shipping “private data” features today without full end-to-end encryption is a reasonable constraint tradeoff. I’ll take a look at Peergos — appreciate the pointer.
2. 2.▲
   by allen-chen 10mo ago

   That’s interesting — especially if you’re already thinking about the e2e step on top of ATProto PDS. At the permissions layer, I’m curious how much of that design you expect to carry over once decryption keys are involved. Happy to follow u
3. 3.▲
   by allen-chen 10mo ago

   Agreed — UX vs. revocation seems to be the core blocker. The JIT/shared-key approach makes revocation much cleaner, but it also shifts trust to a controlled environment rather than purely client-held keys. Have you seen this used beyon
4. 4.▲
   Ask HN: How do teams revoke access to long-lived encrypted cloud data?

   2 points by allen-chen 10mo ago|6 comments