BeeBuzz E2E: from a 4KB limit to end-to-end encryption

This page cannot be shown here. You can still read it on the original site — the toolbar below keeps your place in the directory.

BeeBuzz E2E is shaped by a hard limit: 4KB. That’s the maximum size of a Web Push payload. You can’t encrypt a full notification and send it directly — it won’t fit. The architecture follows from that constraint. The starting constraint Encrypted content can’t travel inside the push payload. So it doesn’t. The encrypted content is stored as a separate attachment The…

Read on /blog/beebuzz-e2e-encryption-architecture/ ↗