Secure Communication

Sever responsibilities

• Retrieve messages
• Store messages
• Profile information
• Web of trust data

Much like the projects I've worked on in the past - everything is done on the client in JavaScript. To prevent coercion, the source is open, in a repository - any questionable check-ins will betray their own intentions.

Some challenges

• indexing/searching

I want to make the protocol open so that anyone can set up a server.

API

• send a message
• request a message
• request a set of message IDs
• request data file (indexes, read message log)