summaryrefslogtreecommitdiffhomepage
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-02 17:27:37 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-02 17:27:37 -0400
commit4b828a123be460e68fe5fd0d17812003ca877ee8 (patch)
tree9079356a742558abd485702cc8871ab940a935f8 /doc
parent63b8a7e037563d40f240dd5ae2e3befc9ff9f5fb (diff)
downloaddebug-me-4b828a123be460e68fe5fd0d17812003ca877ee8.tar.gz
/quit
This commit was sponsored by Jake Vosloo on Patreon.
Diffstat (limited to 'doc')
-rw-r--r--doc/index.mdwn9
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn
index 7dafc20..f594425 100644
--- a/doc/index.mdwn
+++ b/doc/index.mdwn
@@ -28,15 +28,6 @@ to let them type into your console in a debug-me session. Once the
session is done, the debug-me server will email you the signed
evidence of what the developer did in the session.
-It's a good idea to watch the debug-me session. The developer should be
-running their buggy program in different ways, perhaps running a debugger,
-or looking at configuration files. They should *not* be looking at your
-personal files without asking you first in the debug-me chat window.
-They should not be downloading or installing other software. If you see
-them do anything you don't expect, press Control-S immediately, which
-will prevent them from doing anything else. You can also press
-Control-Backslash to immediately end the debug-me session.
-
If the developer did do something bad, you'd have proof that they cannot
be trusted, which you can share with the world. Knowing that is the case
will keep most developers honest.