3 ms·

Considering it went through two major versions in mere hours, the changelog specifying POC changes (instead of spec changes) and for some random reason switched

Considering it went through two major versions in mere hours, the changelog specifying POC changes (instead of spec changes) and for some random reason switched from WS to (fetch functions?) I'm pretty confident that there is no thought behind this. I dig the idea, I dont dig the goal (reinvent email because it's "hard"?), and I don't dig everything after that. Just write a spec at this point, the POC does nothing more than exist for existence sake

wokki20 8mo ago
The spec exists at docs/PROTOCOL.md, and the README itself covers the wire format, cryptographic scheme, and security architecture in detail. HTTP and WebSocket aren't interchangeable choices here: HTTP handles send/API calls, WebSocket handles real-time push delivery. They coexist intentionally. The version jumps look like churn from the outside but 2.0 and 2.1 each landed substantial additions (persistent inboxes + mesh networking, then integrity chain + E2E encryption). Fair to be skeptical of the "reinvent email" motivation, that's a real conversation worth having, but the architecture criticism doesn't hold up on closer reading.