diff --git a/doc/todo/generic_readonly_http_remote/comment_1_5fcd23950ed5409e52d7954abf71afa9._comment b/doc/todo/generic_readonly_http_remote/comment_1_5fcd23950ed5409e52d7954abf71afa9._comment
new file mode 100644
index 0000000000..1199d859ef
--- /dev/null
+++ b/doc/todo/generic_readonly_http_remote/comment_1_5fcd23950ed5409e52d7954abf71afa9._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-07-01T19:05:44Z"
+ content="""
+This overlaps with [[publicurl_config_for_all_special_remotes]]
+but I think is a better approach, at least for most special remotes that is
+could support.
+"""]]
diff --git a/doc/todo/publicurl_config_for_all_special_remotes/comment_5_1d9186506f8f44415706f3b4394c9008._comment b/doc/todo/publicurl_config_for_all_special_remotes/comment_5_1d9186506f8f44415706f3b4394c9008._comment
new file mode 100644
index 0000000000..aef3f989d9
--- /dev/null
+++ b/doc/todo/publicurl_config_for_all_special_remotes/comment_5_1d9186506f8f44415706f3b4394c9008._comment
@@ -0,0 +1,21 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2020-07-01T18:59:48Z"
+ content="""
+[[generic_readonly_http_remote]] if implemented would accomplish the same
+thing as this todo.
+
+The advantage to that idea is, it doesn't need modifications be made to every
+special remote that might end up exposed over http. As long as the special
+remote is not *too* special about how it mangles keys into paths, it
+can work for a lot of special remotes.
+
+The directory special remote is a good example.. It would be weird for that to
+have http-specific configuration and complications.
+
+And, that approach doesn't complicate the external special remote protocol,
+and avoids the problems discussed in comment #4.
+
+So, I'm inclined to that approach over this one.
+"""]]