summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-02 17:02:59 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-02 17:02:59 -0400
commit63b8a7e037563d40f240dd5ae2e3befc9ff9f5fb (patch)
tree607194c6209f45c7bb34d22197b03f6a39866dfc
parentf559fcfadd7079140ed64bab68275527f46d334e (diff)
downloaddebug-me-63b8a7e037563d40f240dd5ae2e3befc9ff9f5fb.tar.gz
split out todo item
-rw-r--r--TODO14
-rw-r--r--doc/todo/send_to_multiple_servers.mdwn15
2 files changed, 15 insertions, 14 deletions
diff --git a/TODO b/TODO
index b048106..c7edc44 100644
--- a/TODO
+++ b/TODO
@@ -1,17 +1,3 @@
-* 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.
* When the user presses control-s, before forwarding it to the terminal,
stop accepting any developer input. Control-s again to resume.
(Or, add buttons to the control window to do this.)
diff --git a/doc/todo/send_to_multiple_servers.mdwn b/doc/todo/send_to_multiple_servers.mdwn
new file mode 100644
index 0000000..94beb2a
--- /dev/null
+++ b/doc/todo/send_to_multiple_servers.mdwn
@@ -0,0 +1,15 @@
+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.