fd49b0140e
* 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. |
||
|---|---|---|
| .. | ||
| applicationmetadata | ||
| datasync | ||
| encryption | ||
| identity | ||
| internal/sqlite | ||
| migrations | ||
| protobuf | ||
| sqlite | ||
| subscription | ||
| transport/whisper | ||
| tt | ||
| v1 | ||
| zaputil | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| chat.go | ||
| chat_group_proxy.go | ||
| contact.go | ||
| go.mod | ||
| go.sum | ||
| message.go | ||
| message_handler.go | ||
| message_processor.go | ||
| message_processor_test.go | ||
| messenger.go | ||
| messenger_test.go | ||
| migrations.go | ||
| migrations_test.go | ||
| persistence.go | ||
| persistence_legacy.go | ||
| persistence_legacy_test.go | ||
README.md
status-go/protocol
This is the Status Protocol implementation in Go.
TBD