Really like the Nostr approach here. The trustless calendar coordination problem is thornier than most people realize – you need to handle timezone conversions, availability windows, and preference weighting without leaking private schedule data to a central server.
One question: how are you handling the case where someone's availability changes after they've shared slots? With end-to-end encryption, you can't really do server-side invalidation. Are you relying on clients to broadcast updates, or is there a different pattern you're using?
I've been working on encrypted document workflows and ran into similar state synchronization challenges when you can't trust the intermediary.
One question: how are you handling the case where someone's availability changes after they've shared slots? With end-to-end encryption, you can't really do server-side invalidation. Are you relying on clients to broadcast updates, or is there a different pattern you're using?
I've been working on encrypted document workflows and ran into similar state synchronization challenges when you can't trust the intermediary.