diff --git a/doc/forum/standalone_tarballs_for_specific_versions/comment_2_211e260fbc60dc83a8986fac4e9700b7._comment b/doc/forum/standalone_tarballs_for_specific_versions/comment_2_211e260fbc60dc83a8986fac4e9700b7._comment
new file mode 100644
index 0000000000..b85bf8dae7
--- /dev/null
+++ b/doc/forum/standalone_tarballs_for_specific_versions/comment_2_211e260fbc60dc83a8986fac4e9700b7._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="URL for git-annex-standalone for specific version"
+ date="2020-03-04T01:33:30Z"
+ content="""
+`git-annex-whereis` does not seem to report a URL... how do I find it?
+
+[[!format sh \"\"\"
+(base) 20:26  [downloads.kitenet.net] $ git annex whereis /data/sw/ga-archive/downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz
+whereis git-annex/linux/current/git-annex-standalone-amd64.tar.gz (1 copy)
+        840760dc-08f0-11e2-8c61-576b7e66acfd -- main repo [origin]
+\"\"\"]]
+
+Reason for needing a stable per-version URL is that conda recipes require one.
+"""]]
diff --git a/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn b/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn
index 87908a8365..8740839421 100644
--- a/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn
+++ b/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn
@@ -9,15 +9,18 @@ I wanted to understand what the individual setup steps are doing in detail. I ho
 This is what the **enable-tor** command does:
 
 Be
-hiddenServiceSocketFile=/var/lib/tor-annex/$(id -u)_$(git config --get annex.uuid)/s
+`hiddenServiceSocketFile=/var/lib/tor-annex/$(id -u)_$(git config --get annex.uuid)/s`
 
 - prepHiddenServiceSocketDir effectively does
-  mkdir -p $(dirname $hiddenServiceSocketFile)
+
+  `mkdir -p $(dirname $hiddenServiceSocketFile)`
 
 - adds two lines to /etc/tor/torrc
 
+  ```
   HiddenServiceDir /var/lib/tor/tor-annex_$(id -u)_$(git config --get annex.uuid)
   HiddenServicePort $newport unix:$hiddenServiceSocketFile
+  ```
 
 - restarts the tor service and waits for it to come back
 
@@ -32,9 +35,11 @@ hiddenServiceSocketFile=/var/lib/tor-annex/$(id -u)_$(git config --get annex.uui
   
   Confirmed in comment in Auth.hs:
   
+  ```
   -- We can omit the port and just use the onion address for the creds file,
   -- because any given tor hidden service runs on a single port and has a
   -- unique onion address.
+  ```
 
 - Wouldn't it be easier if git-annex-remotedaemon would just run a child tor
   process? This way git-annex would fully control the config file and there were
@@ -46,7 +51,7 @@ hiddenServiceSocketFile=/var/lib/tor-annex/$(id -u)_$(git config --get annex.uui
 
 ## git-annex-p2p --pair
 
-Man page: https://git-annex.branchable.com/git-annex-p2p
+Man page: <https://git-annex.branchable.com/git-annex-p2p>
 
 I did not use the --pair option since it was unclear to me what exact Wormhole version was needed. Also it was to magic for me.
 So far I did the pairing only in one direction and still the synchronization seems to work at least in one direction. I don't remember ATM whether I also tested the other direction.
@@ -76,7 +81,7 @@ I needed some time to find out that I need to configure "annex-tracking-branch"
 
 ## Links
 
-https://git-annex.branchable.com/special_remotes/tor/
-https://git-annex.branchable.com/tips/peer_to_peer_network_with_tor/
-https://2019.www.torproject.org/docs/onion-services
-https://riseup.net/en/security/network-security/tor/onionservices-best-practices
+- <https://git-annex.branchable.com/special_remotes/tor>
+- <https://git-annex.branchable.com/tips/peer_to_peer_network_with_tor>
+- <https://2019.www.torproject.org/docs/onion-services>
+- <https://riseup.net/en/security/network-security/tor/onionservices-best-practices>
diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_8_5592ac9d1887183daf3173a0c27b672f._comment b/doc/todo/shorter_keys_through_better_encoding/comment_8_5592ac9d1887183daf3173a0c27b672f._comment
new file mode 100644
index 0000000000..b3435bca6a
--- /dev/null
+++ b/doc/todo/shorter_keys_through_better_encoding/comment_8_5592ac9d1887183daf3173a0c27b672f._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="amerlyq+annex@12121d70a602f094228689a0a24d348d478a8af1"
+ nickname="amerlyq+annex"
+ avatar="http://cdn.libravatar.org/avatar/3d63c9f436b45570d45bd003e468cbd3"
+ subject="re: shorter symlinks"
+ date="2020-03-04T00:48:02Z"
+ content="""
+I don't need strategy nor safety.
+Create a tunable for new repos to disable directory sha completely (and if not sustainable - even readonly bit safety) - and that is enough.
+I will replay whole my history again onto new repo and make fs snapshotting more frequently.
+I can even live without base64.
+Changing defaults is undesirable - and that is understandable. 
+But we would still prefer to have an option, even if to bear the whole grunt of consequences ourselves.
+Sometimes I wonder if it worth to learn Haskell only to fork gitannex for specific needs, but the reason for this encompassing endeavor seems lame :(
+"""]]