diff --git a/doc/backends/comment_30_bea2a3f4f673e6e9d5ee99cf10d39460._comment b/doc/backends/comment_30_bea2a3f4f673e6e9d5ee99cf10d39460._comment
new file mode 100644
index 0000000000..0e56f6989d
--- /dev/null
+++ b/doc/backends/comment_30_bea2a3f4f673e6e9d5ee99cf10d39460._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="annex2384@290036d126d86bcec28ee2f2ead549de1f59e90e"
+ nickname="annex2384"
+ avatar="http://cdn.libravatar.org/avatar/ad36fdc55abd8b9913b774fcd0177709"
+ subject="Backend which doesn't stoee files at all?"
+ date="2020-02-20T14:52:21Z"
+ content="""
+I'd like to be able to have a \"thin\" repo on a FAT32 filesystem. Since this precludes hardlinks, is there a way to make a backend that just keeps track of the file's hash so we can detect when it changes? This would obviously need to rely on having copies in other repos for backup purposes. I'm thinking a mode that behaves more like Unison, which just used its fingerprint file to detect changes that need to be synced.
+
+There would still be a file in the backend named by SHA256, but instead of storing the content it would store the location of possible local copies of the file. This would obviously need to use a smudge filter. It could be the default backend for thin repos on filesystems that don't support hardlinks.
+
+"""]]
diff --git a/doc/forum/annex.largefile_include_from_file.mdwn b/doc/forum/annex.largefile_include_from_file.mdwn
new file mode 100644
index 0000000000..47e6b4bc1a
--- /dev/null
+++ b/doc/forum/annex.largefile_include_from_file.mdwn
@@ -0,0 +1,5 @@
+Hello!
+
+     Is it possible to configure `annex.largefiles` to include or exclude any patterns from a file?
+
+Thank you kindly for the help!
diff --git a/doc/forum/annex.largefile_include_from_file/comment_1_9016a64a654151ab9a478686382193b4._comment b/doc/forum/annex.largefile_include_from_file/comment_1_9016a64a654151ab9a478686382193b4._comment
new file mode 100644
index 0000000000..934e3fe9cb
--- /dev/null
+++ b/doc/forum/annex.largefile_include_from_file/comment_1_9016a64a654151ab9a478686382193b4._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="comment 1"
+ date="2020-02-20T01:09:55Z"
+ content="""
+You can set it in `.gitattributes`, or with [[git-annex-config]].
+"""]]
diff --git a/doc/forum/annex.largefile_include_from_file/comment_2_09258e59eab492afc37efeac325c2de1._comment b/doc/forum/annex.largefile_include_from_file/comment_2_09258e59eab492afc37efeac325c2de1._comment
new file mode 100644
index 0000000000..09cfc8be6c
--- /dev/null
+++ b/doc/forum/annex.largefile_include_from_file/comment_2_09258e59eab492afc37efeac325c2de1._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="titaniumfiles@5227364ee3e2f9207bc36b6ebb281fc7af6d3c16"
+ nickname="titaniumfiles"
+ avatar="http://cdn.libravatar.org/avatar/067eaf551eb18de259f4d88966622326"
+ subject="comment 2"
+ date="2020-02-20T02:02:05Z"
+ content="""
+But how would I get `include` to read from a file?
+"""]]
diff --git a/doc/forum/annex.largefile_include_from_file/comment_3_f857505bde5f03d9c17e8df0512c0e99._comment b/doc/forum/annex.largefile_include_from_file/comment_3_f857505bde5f03d9c17e8df0512c0e99._comment
new file mode 100644
index 0000000000..82b3ee9167
--- /dev/null
+++ b/doc/forum/annex.largefile_include_from_file/comment_3_f857505bde5f03d9c17e8df0512c0e99._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="comment 3"
+ date="2020-02-20T03:50:50Z"
+ content="""
+Why, exactly, do you need to do that?   Can you say more about your scenario?
+"""]]
diff --git a/doc/forum/auto-fetching_annexed_files_on_open__40____41__.mdwn b/doc/forum/auto-fetching_annexed_files_on_open__40____41__.mdwn
new file mode 100644
index 0000000000..074e50a012
--- /dev/null
+++ b/doc/forum/auto-fetching_annexed_files_on_open__40____41__.mdwn
@@ -0,0 +1,8 @@
+It would make git-annex much simpler to use if annexed files could be transparently auto-fetched when programs try to read them, without requiring an explicit `git-annex-get`.
+
+What approaches have people tried to make this work, and what were the results / takeaways?
+
+Some related pages: [[news/sharebox_a_FUSE_filesystem_for_git-annex]]; [[todo/union_mounting]]; [[using fanotify|forum/expire_files__44___move_to_other_hosts]] .
+
+My attempt at a FUSE filesystem that calls `git-annex-get` as needed: [here](https://github.com/broadinstitute/viral-ngs/blob/is-dx-benchmarks/tools/git-annex-remotes/git-annex-on-demand.py).  However, it gets an annexed file as soon as a symlink to it is read, which can also happen when just listing a directory; it also only works with locked annexed files.
+