diff --git a/doc/bugs/One_Client_Not_Syncing_Content/comment_4_0a5cec1d4496b89ccfec3f607cb7a87c._comment b/doc/bugs/One_Client_Not_Syncing_Content/comment_4_0a5cec1d4496b89ccfec3f607cb7a87c._comment
new file mode 100644
index 0000000000..0b129f882e
--- /dev/null
+++ b/doc/bugs/One_Client_Not_Syncing_Content/comment_4_0a5cec1d4496b89ccfec3f607cb7a87c._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="stephenriley"
+ avatar="http://cdn.libravatar.org/avatar/b1650df547698382f40f305fa96dbc8c"
+ subject="comment 4"
+ date="2023-06-15T02:57:25Z"
+ content="""
+Players may enjoy the rush of drifting in the online game drift hunters. While there are other drift games available, Drift Hunters provides something special and thrilling.
+"""]]
diff --git a/doc/bugs/One_Client_Not_Syncing_Content/comment_5_259be719dfb6bd7e304c540c73229719._comment b/doc/bugs/One_Client_Not_Syncing_Content/comment_5_259be719dfb6bd7e304c540c73229719._comment
new file mode 100644
index 0000000000..5ff260a264
--- /dev/null
+++ b/doc/bugs/One_Client_Not_Syncing_Content/comment_5_259be719dfb6bd7e304c540c73229719._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="stephenriley"
+ avatar="http://cdn.libravatar.org/avatar/b1650df547698382f40f305fa96dbc8c"
+ subject="comment 5"
+ date="2023-06-15T02:57:35Z"
+ content="""
+Players may enjoy the rush of drifting in the online game drift hunters. While there are other drift games available, Drift Hunters provides something special and thrilling.
+"""]]
diff --git a/doc/bugs/assistant_committer_crashes_due_to_missing_file.mdwn b/doc/bugs/assistant_committer_crashes_due_to_missing_file.mdwn
new file mode 100644
index 0000000000..36f45d8183
--- /dev/null
+++ b/doc/bugs/assistant_committer_crashes_due_to_missing_file.mdwn
@@ -0,0 +1,69 @@
+### Please describe the problem.
+
+The git annex assistant committer stops working and crashes under certain circumstances when dealing with small files.
+
+This seems to occur when a small file is in the committer queue but is deleted before the queue is flushed.
+
+### What steps will reproduce the problem?
+
+Set the `annex.largefiles` option to exclude certain files from the annex: `git config annex.largefiles 'exclude=*.txt'`.
+
+Create and immediately delete some file that is excluded from the annex:
+
+[[!format sh """
+touch somefile.txt && rm somefile.txt
+"""]]
+
+This will cause a "user error" to occur every time the committer thread tries to do a commit, essentially causing it to stop working.
+
+In addition, if no file activity occurs for 5 minutes, creating another file will cause the committer to crash:
+
+[[!format sh """
+sleep 310
+touch someotherfile.txt
+"""]]
+
+### What version of git-annex are you using? On what operating system?
+
+Operating system: Arch Linux x86_64
+
+git-annex version: 10.20230329
+
+### Please provide any additional information below.
+
+[[!format sh """
+# .git/annex/daemon.log
+
+[2023-06-14 17:32:42.652269404] (Watcher) add somefile.txt
+[2023-06-14 17:32:42.652761285] (Watcher) add somefile.txt
+[2023-06-14 17:32:42.652832039] (Watcher) file deleted somefile.txt
+[2023-06-14 17:32:42.663222161] (Utility.Process) process [1178267] read: lsof ["-F0can","+d",".git/annex/watchtmp/"]
+[2023-06-14 17:32:42.830892116] (Utility.Process) process [1178267] done ExitFailure 1
+[2023-06-14 17:32:42.831219136] (Utility.Process) process [1178269] feed: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","update-index","-z","--index-info"]
+[2023-06-14 17:32:42.832078397] (Utility.Process) process [1178269] done ExitSuccess
+[2023-06-14 17:32:42.832140832] (Committer) committing 2 changes
+(recording state in git...)
+[2023-06-14 17:32:42.832442128] (Utility.Process) process [1178270] feed: xargs ["-0","git","--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","add","--force","--"]
+fatal: pathspec 'somefile.txt' did not match any files
+[2023-06-14 17:32:42.833714128] (Utility.Process) process [1178270] done ExitFailure 123
+[2023-06-14 17:33:10.166497909] (Utility.Process) process [1178219] done ExitSuccess
+[2023-06-14 17:33:10.167361436] (Utility.Process) process [1178207] done ExitSuccess
+[2023-06-14 17:33:10.168264148] (Utility.Process) process [1178218] done ExitSuccess
+[2023-06-14 17:33:10.16909154] (Utility.Process) process [1178238] done ExitSuccess
+[2023-06-14 17:33:10.169892592] (Utility.Process) process [1178240] done ExitSuccess
+[2023-06-14 17:33:10.170694357] (Utility.Process) process [1178227] done ExitFailure 1
+[2023-06-14 17:33:40.185689237] (Utility.Process) process [1178330] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","ls-tree","--full-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","numcopies.log","mincopies.log","schedule.log","preferred-content.log","required-content.log","group-preferred-content.log"]
+[2023-06-14 17:33:40.189177926] (Utility.Process) process [1178330] done ExitSuccess
+[2023-06-14 17:37:52.65735194] (Utility.Process) process [1178648] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","cat-file","--batch-check=%(objectname) %(objecttype) %(objectsize)"]
+[2023-06-14 17:37:52.660710625] (Utility.Process) process [1178649] chat: git ["--git-dir=.git","--work-tree=.","-c","annex.debug=true","check-ignore","-z","--stdin","--verbose","--non-matching"]
+[2023-06-14 17:37:52.663100743] (Watcher) add someotherfile.txt
+[2023-06-14 17:37:52.663984987] (Watcher) add someotherfile.txt
+[2023-06-14 17:37:52.674996448] (Utility.Process) process [1178650] read: lsof ["-F0can","+d",".git/annex/watchtmp/"]
+[2023-06-14 17:37:52.825736165] (Utility.Process) process [1178650] done ExitFailure 1
+[2023-06-14 17:37:52.826111004] (Utility.Process) process [1178652] feed: xargs ["-0","git","--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","add","--force","--"]
+fatal: pathspec 'somefile.txt' did not match any files
+[2023-06-14 17:37:52.82750231] (Utility.Process) process [1178652] done ExitFailure 123
+Committer crashed: user error (xargs ["-0","git","--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","annex.debug=true","add","--force","--"] exited 123)
+
+# End of transcript or log.
+"""]]
diff --git a/doc/copies/comment_2_1214610c03193cb9dd76dc24e5b7fd76._comment b/doc/copies/comment_2_1214610c03193cb9dd76dc24e5b7fd76._comment
new file mode 100644
index 0000000000..8f250b9de7
--- /dev/null
+++ b/doc/copies/comment_2_1214610c03193cb9dd76dc24e5b7fd76._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="tomdhunt"
+ avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3"
+ subject="Differing reliability among remotes"
+ date="2023-06-12T22:58:41Z"
+ content="""
+I'm looking for a way to express that remotes may be of differing reliability. E.g. some remotes are on RAIDs that are robust to disk failures, but others are on single, possibly external disks. I would like copies of a file on a reliable remote to count for more than those on an unreliable one, so that e.g. git-annex requires two copies on single disks but allows one on a RAID.
+
+Is there a way to do this via the copies logic? Or some other method?
+"""]]
diff --git a/doc/copies/comment_3_5beb9a5b87dd6775f9b921ad1e9bc610._comment b/doc/copies/comment_3_5beb9a5b87dd6775f9b921ad1e9bc610._comment
new file mode 100644
index 0000000000..287e89e25f
--- /dev/null
+++ b/doc/copies/comment_3_5beb9a5b87dd6775f9b921ad1e9bc610._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="nobodyinperson"
+ avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
+ subject="comment 3"
+ date="2023-06-13T06:42:47Z"
+ content="""
+git annex can't have multiple copies of the same file in one repo. And if your disk fails, a second copy doesn't really help, does it? But you can achieve what you want with either:
+
+- kinda with `git annex untrust repo-on-normal-disk`, this will assume your normal disks might fail anytime and will put files elsewhere as well
+- with [groups](https://git-annex.branchable.com/preferred_content/standard_groups/)
+ - make another, second repo on your normal disks (that alone could help)
+ - put all repos on your normal disks into one group: `git annex group mydisk1 baddisks` and `git annex group mydisk2 baddisks`
+ - specify that all your normal disks want to have the same content as the raid ones with some expression: https://git-annex.branchable.com/preferred_content/ `git annex groupwanted baddisks ...` `git annex wanted myrepo1 groupwanted`
+"""]]
diff --git a/doc/copies/comment_4_0daa1b3ecc2a4cf844b8f1b98a883e67._comment b/doc/copies/comment_4_0daa1b3ecc2a4cf844b8f1b98a883e67._comment
new file mode 100644
index 0000000000..4825b572b1
--- /dev/null
+++ b/doc/copies/comment_4_0daa1b3ecc2a4cf844b8f1b98a883e67._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="strmd"
+ avatar="http://cdn.libravatar.org/avatar/035707b9756129bbdea6b36a7f7b38d3"
+ subject="comment 4"
+ date="2023-06-14T10:42:40Z"
+ content="""
+A quick thought: Perhaps it might be worth exploring if `trust` could be like implemented in a way similar to `cost`. It might open up possibilities for setting a required level of trust for a given file, adding up the various remotes to a sum.
+"""]]
diff --git a/doc/forum/only_keep_current_version_of_files_in_repo/comment_1_dd03f7cd46a8c12a34e2b1cf78e7a057._comment b/doc/forum/only_keep_current_version_of_files_in_repo/comment_1_dd03f7cd46a8c12a34e2b1cf78e7a057._comment
new file mode 100644
index 0000000000..4a5f95a4b0
--- /dev/null
+++ b/doc/forum/only_keep_current_version_of_files_in_repo/comment_1_dd03f7cd46a8c12a34e2b1cf78e7a057._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="aurtzy"
+ avatar="http://cdn.libravatar.org/avatar/7d44f9b718a534ada04551ee8c72e07f"
+ subject="comment 1"
+ date="2023-06-15T01:56:43Z"
+ content="""
+Hi! It sounds like what you want is the client [standard group](/preferred_content/standard_groups/) without the archive exclusion part? If so, this should work: `git-annex wanted server \"include=*\"`
+"""]]
diff --git a/doc/todo/arm64_autobuild_broken_since_2022/comment_2_48e40f76e0480adc965505543a4f25e5._comment b/doc/todo/arm64_autobuild_broken_since_2022/comment_2_48e40f76e0480adc965505543a4f25e5._comment
new file mode 100644
index 0000000000..355879eeb8
--- /dev/null
+++ b/doc/todo/arm64_autobuild_broken_since_2022/comment_2_48e40f76e0480adc965505543a4f25e5._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="nobodyinperson"
+ avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
+ subject="comment 2"
+ date="2023-06-12T21:12:29Z"
+ content="""
+Huh, this is very weird. I could've sworn that the date 202201 was all over the place this morning and was also the version one got when downloading the standalone arm64 version or the autobuild version. But now everything seems to be fine. Sorry for the confusion, then.
+"""]]