summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-04-28 00:56:56 -0400
committerJoey Hess <joeyh@joeyh.name>2017-04-28 00:56:56 -0400
commitbb5e2553d637f354ea3b373064ef4848f2128bdf (patch)
treee5baf31ae61366774c9f50081c3a59594cba9bf1
parent3f3f47cf5242a209373db74656f7c237500119b7 (diff)
downloaddebug-me-bb5e2553d637f354ea3b373064ef4848f2128bdf.tar.gz
todo
-rw-r--r--TODO18
1 files changed, 14 insertions, 4 deletions
diff --git a/TODO b/TODO
index 5a070da..1a9d597 100644
--- a/TODO
+++ b/TODO
@@ -49,7 +49,17 @@
log files for long, this makes them unattractive to abusers
who might otherwise try to store large quantities of data.
-* --server --replicate=host could connect to the other server and forward
- sessions to it. It should be easy to make the replicate bi-directional,
- so a developer could connect to the other server and their messages be
- sent back to the first server.
+* Client should upload to multiple servers, for redundancy. This way,
+ if Joey runs a server, and Alice runs a server, the user can start
+ debug-me and not worry that Joey will connect, do something bad, and have
+ his server cover it up, because Alice's server will also get the data.
+
+ When Bob connects to Alice's server and sends messages to the client,
+ it should then repeat those same messages to Joey's server (but not back
+ to Alice's server).
+
+ This will use some more bandwidth of course. Inter-server replication
+ could also be done to avoid using client bandwidth. But then, if the
+ client only sent to Joey's server and trusted it to replicate to Alice,
+ Joey could break the replication to cover up his nefarious activities
+ in the debug-me session.