Andrea Maria Piana f5ab58b87f Add support for images
This commit adds support for images in protobuf messages.

The client can specify a path which will be used to load the image
and set the corresponding fields.

This makes the assumption that the RCP server runs on the same machine
as the client and they have access to the same files. This holds
currently for both status-react and status-console-client, we could
revisit and adds an upload if that changes in the future.
2020-06-01 11:30:04 +02:00
..
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-02-21 15:48:53 +01:00
2020-06-01 11:30:04 +02:00
2019-11-21 17:19:22 +01:00
2020-02-07 12:56:30 +01:00
2020-05-25 14:00:04 +02:00
2019-11-21 17:19:22 +01:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-06-01 11:30:04 +02:00
2020-05-25 14:00:04 +02:00
2020-01-16 13:18:36 +01:00

status-go/protocol

This is an implementation of the secure transport and payloads which are a part of the Status Client specification.

This implementation uses SQLite and SQLCipher for persistent storage.

The payloads are encoded using protocol-buffers.

Content

  • messenger.go is the main file which exports Messenger struct. This is a public API to interact with this implementation of the Status Chat Protocol.
  • protobuf/ contains protobuf files implementing payloads described in the Payloads spec.
  • encryption/ implements the Secure Transport spec.
  • transport/ connects the Status Chat Protocol with a wire-protocol which in our case is either Whisper or Waku.
  • datasync/ is an adapter for MVDS.
  • applicationmetadata/ is an outer layer wrapping a payload with an app-specific metadata like a signature.
  • identity/ implements details related to creating a three-word name and identicon.
  • migrations/ contains implementation specific migrations for the sqlite database which is used by Messenger as a persistent data store.