ricochet-go/core
John Brooks d8a14fb4c5 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.
2017-09-24 17:00:44 -06:00
..
config core: Reuse protobuf structures for configuration 2017-09-24 16:59:44 -06:00
utils core: Use consistent functions to validate and convert address formats 2016-11-05 21:27:13 -06:00
address.go core: Use consistent functions to validate and convert address formats 2016-11-05 21:27:13 -06:00
contact-protocol.go Implement conversation with the new protocol API 2017-09-23 19:18:24 -06:00
contact.go Remove the concept of numeric contact IDs 2017-09-24 17:00:44 -06:00
contactlist.go Remove the concept of numeric contact IDs 2017-09-24 17:00:44 -06:00
conversation.go Implement conversation with the new protocol API 2017-09-23 19:18:24 -06:00
identity.go core: Reuse protobuf structures for configuration 2017-09-24 16:59:44 -06:00
inboundcontactrequest.go core: Reuse protobuf structures for configuration 2017-09-24 16:59:44 -06:00
network.go core: Fix generation of new onion keys 2017-09-24 16:56:29 -06:00
onionconnector.go core: Improve OnionConnector backoff and retry behavior 2016-11-06 19:35:15 -07:00
ricochet.go core: Reuse protobuf structures for configuration 2017-09-24 16:59:44 -06:00
rpcserver.go Remove the concept of numeric contact IDs 2017-09-24 17:00:44 -06:00
sanitize.go core: Actually define maximum nick/message lengths 2016-12-27 17:56:44 -07:00