aboutsummaryrefslogtreecommitdiff
path: root/spec/path-spec/old-notes.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/path-spec/old-notes.md')
-rw-r--r--spec/path-spec/old-notes.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/spec/path-spec/old-notes.md b/spec/path-spec/old-notes.md
index 34734fb..ce3ec44 100644
--- a/spec/path-spec/old-notes.md
+++ b/spec/path-spec/old-notes.md
@@ -26,15 +26,15 @@ How to deal with network down.
circuit and beginning to use it immediately?)
```
-[Do we actually do any of the above? If so, let's spec it. If not, let's
-remove it. -NM]
+\[Do we actually do any of the above? If so, let's spec it. If not, let's
+remove it. -NM\]
<a id="path-spec.txt-X.2"></a>
## A thing we could do to deal with reachability
And as a bonus, it leads to an answer to Nick's attack ("If I pick
-my helper nodes all on 18.0.0.0:*, then I move, you'll know where I
+my helper nodes all on 18.0.0.0:\*, then I move, you'll know where I
bootstrapped") -- the answer is to pick your original three helper nodes
without regard for reachability. Then the above algorithm will add some
more that are reachable for you, and if you move somewhere, it's more
@@ -59,5 +59,5 @@ our location (IP? subnet?) changes, we have two bad options. We could
nasty, since it would force us to record where we've been.
```
-[Do we do any of this now? If not, this should move into 099-misc or
-098-todo. -NM]
+\[Do we do any of this now? If not, this should move into 099-misc or
+098-todo. -NM\]