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
2019-05-15 11:01:34 +02:00
2018-03-23 14:58:40 +01:00
2018-06-08 19:10:29 +03:00
2019-11-15 13:18:08 +01:00
2019-06-12 13:12:00 +02:00
2016-09-21 10:00:29 +08:00
Description
The Status module that consumes go-ethereum
https://status.im
Readme
Languages
Go 98.7%
Python 0.7%
Shell 0.3%
Makefile 0.1%
Groovy 0.1%