dan
/
ricochet-go
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
24 Commits 2 Branches 0 Tags 2.3 MiB
Go 95.6%
Protocol Buffer 4.4%
Go to file
John Brooks 6e68f861d8 rpc: Add UNKNOWN connection status for contacts 
UNKNOWN is the new default status for contacts. A contact is in the
UNKNOWN state when we're not sure whether they are available or not, and
is in the OFFLINE state when we believe that we're online but attempts
to connect to that contact have failed.
 		2016-09-15 18:30:37 -06:00
backend core: Change the 'Ricochet' API again 2016-09-10 23:00:26 -06:00
cli core: Load contacts from config 2016-08-29 20:46:41 -06:00
core core: Refactor network reconnection to fix onion republication 2016-09-15 18:16:00 -06:00
rpc rpc: Add UNKNOWN connection status for contacts 2016-09-15 18:30:37 -06:00
.gitignore gitignore 2016-08-02 17:36:28 -06:00
README.md Fix README markup. 2016-08-03 01:39:03 +02:00

README.md

This is an idea for the architecture of a Ricochet client. Don't get excited. It doesn't do anything.

The idea is to implement all client backend logic in Go, and export a RPC API for frontends.

Benefits:

  • We can have all network-facing and critical logic in Go, without being forced to use Go for frontends (because it lacks decent UI capability)
  • We can keep the current Qt UI implementation as one frontend
  • It's easy to build new frontends in anything that can use gRPC (like cli)
  • Backends are headless and frontends are detachable and interchangable
  • Can do some fancy sandboxing

Other ideas:

  • This is currently using RPC only for the backend<->frontend; would it make sense to RPC any other layers or distinct components? Could have security benefits.
  • In particular, we still have one process that has access to private keys, tor config, and untrusted network traffic. That sucks.
  • Can do frontend connection to backend over authorized onion for advanced setups

Structure:

  • core is the client logic implementation
  • rpc has gRPC/protobuf definitions & generated code
  • backend is the backend RPC server
  • cli is an example frontend client