status-go/vendor
Andrea Maria Piana fd49b0140e
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`

* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.

* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.

* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 17:25:34 +01:00
..
github.com Move to protobuf for Message type (#1706) 2019-12-05 17:25:34 +01:00
go.opencensus.io Upgrade geth to 1.9.5 and Whisper (#1617) 2019-10-04 17:21:24 +02:00
go.uber.org Upgrade zap to v1.13.0 (#1694) 2019-11-25 21:16:00 +01:00
golang.org/x Move to protobuf for Message type (#1706) 2019-12-05 17:25:34 +01:00
gopkg.in Verify ens endpoint, only against mainnet (#1657) 2019-11-04 11:08:22 +01:00
honnef.co/go/tools Upgrade zap to v1.13.0 (#1694) 2019-11-25 21:16:00 +01:00
modules.txt Move to protobuf for Message type (#1706) 2019-12-05 17:25:34 +01:00