dan
/
ricochet-go
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
39 Commits 2 Branches 0 Tags 2.3 MiB
Go 95.6%
Protocol Buffer 4.4%
Go to file
John Brooks 7fe2363801 core: More of the conversation implementation 
Improved parts of the conversation implementation, moved the
conversation event monitor to Identity, added event monitor
population, and other minor changes.
 		2016-10-15 18:04:19 -06:00
backend core: More of the conversation implementation 2016-10-15 18:04:19 -06:00
cli cli: Minimal conversation functionality 2016-10-06 16:50:52 -07:00
core core: More of the conversation implementation 2016-10-15 18:04:19 -06:00
rpc core: Early proof-of-concept conversations API 2016-10-05 14:38:18 -07: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