Proto commits in ricochet-im/ricochet-go

These 12 commits are when the Protocol Buffers files have changed:

2017-09-24

Remove the concept of numeric contact IDs In ricochet-qt, contacts were stored with a sequential numeric ID, and that was used in various places to refer to the contact uniquely. The habit carried over here in an attempt to keep configuration compatibility. These IDs are error prone (particularly over RPC) and unnecessary. This removes the entire concept and uses addresses to index and refer uniquely to contacts everywhere.

The documentation is generated from this commit.

core: Reuse protobuf structures for configuration The existing configuration was partially compatible with Ricochet's, but not enough to actually be useful. It also required a bunch of boilerplate code to copy data between configuration data structures, internal data structures, and RPC data structures. Protobuf conveniently supports encoding messages to JSON, and we already need to store most data (e.g. contacts) in protobuf structures. This commit changes the configuration to be a protobuf JSON serialization of the Config message, which can directly reuse RPC messages like Contact. Additionally, the RWMutex-based configuration type was a deadlock waiting to happen. There is now a read-only clone of the configuration available atomically at any time. Writers need an exclusive lock on the ConfigFile object, which commits its changes to disk and readers on unlock.

2017-08-10

core: Implement inbound contact requests This does not yet include persistence of inbound requests in the config, and it's mostly untested, but it's more or less complete.

2016-11-06

core: Remove outdated todo comments

2016-10-27

rpc: Add 'go generate' commands and update ContactRequest It's now possible to regenerate the protobuf files by calling 'go generate' in rpc/. You will need protoc and protoc-gen-go in PATH. This is only necessary after changing the protobuf definitions.

2016-10-23

cli: Keep track of conversations and prettify output

2016-10-16

core: Track unread state of received messages

2016-10-05

core: Early proof-of-concept conversations API

2016-09-16

rpc: Add UNKNOWN connection status for contacts UNKNOWN is the new default status for contacts. A contact is in the UNKNOWN state when we're not sure whether they are available or not, and is in the OFFLINE state when we believe that we're online but attempts to connect to that contact have failed.

2016-08-30

core: Load contacts from config

2016-08-17

rpc: Draft more RPC API calls

2016-08-02

Skeleton of RPC