diff --git a/doc/design/external_special_remote_protocol/comment_39_ea321b96df3314a9e2a35cd0f8312972._comment b/doc/design/external_special_remote_protocol/comment_39_ea321b96df3314a9e2a35cd0f8312972._comment
new file mode 100644
index 0000000000..04f221bb89
--- /dev/null
+++ b/doc/design/external_special_remote_protocol/comment_39_ea321b96df3314a9e2a35cd0f8312972._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="lykos@d125a37d89b1cfac20829f12911656c40cb70018"
+ nickname="lykos"
+ avatar="http://cdn.libravatar.org/avatar/085df7b04d3408ba23c19f9c49be9ea2"
+ subject="PREPARE-LOCAL"
+ date="2019-01-15T15:47:39Z"
+ content="""
+> \"Note that users expect `git annex whereis` to run fast, without eg, network access\"
+
+Currently, git-annex spins up a remote process for every `git annex whereis` command that involves a file present on the remote (w/o chunking & encryption). As most remotes establish their network connection during the PREPARE phase, the command is slowed down, especially with bad internet connection. So I propose an extension `PREPARE-LOCAL` that tells the remote to get all necessary config information but skip the networking.
+
+Alternatively, the remotes could wait to establish network connection until the first transfer command is sent but I think something like `PREPARE-LOCAL` would be the cleaner solution.
+"""]]
diff --git a/doc/forum/RecentChanges__58___link_to_the_diff__63__/comment_1_85254a327ffed22b407d25610558c15b._comment b/doc/forum/RecentChanges__58___link_to_the_diff__63__/comment_1_85254a327ffed22b407d25610558c15b._comment
new file mode 100644
index 0000000000..4d209148ae
--- /dev/null
+++ b/doc/forum/RecentChanges__58___link_to_the_diff__63__/comment_1_85254a327ffed22b407d25610558c15b._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
+ subject="comment 1"
+ date="2019-01-15T08:30:10Z"
+ content="""
+There already is one. It's right before the link to the page (has 3D glasses image).
+
+    <span class=\"pagelinks\">
+      <a href=\"http://source.git-annex.branchable.com/?p=source.git;a=blobdiff;f=doc/forum/RecentChanges__58___link_to_the_diff__63__.mdwn;h=6c15de14e1b020c43bd11132726d62942ab96f42;hp=0000000000000000000000000000000000000000;hb=27cf71e7e4b1a8e556000375c96bc30bc1b8fae7;hpb=9953e3d3530aa48cd26dd3e69fd81488f83164a9\" title=\"diff\" rel=\"nofollow\">
+        <img src=\"../wikiicons/diff.png\" alt=\"diff\">
+      </a>
+      <a href=\"/ikiwiki.cgi?do=goto&amp;page=forum%2FRecentChanges__58___link_to_the_diff__63__\" rel=\"nofollow\">forum/RecentChanges: link to the diff?</a>
+    </span>
+"""]]
diff --git a/doc/todo/testremote_for_read-only_remotes.mdwn b/doc/todo/testremote_for_read-only_remotes.mdwn
new file mode 100644
index 0000000000..d23e828f3e
--- /dev/null
+++ b/doc/todo/testremote_for_read-only_remotes.mdwn
@@ -0,0 +1 @@
+It's not uncommon to create external special remotes for which, like for the built-in web remote, only download operations are defined.  It would be good if git-annex-testremote had the option of testing such remotes, using as test data the keys and URLs already registered as present in the remote.