diff --git a/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_5_8c33fc01dd1de2abcd3782ff89b437de._comment b/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_5_8c33fc01dd1de2abcd3782ff89b437de._comment
index 170b217649..5645cb6755 100644
--- a/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_5_8c33fc01dd1de2abcd3782ff89b437de._comment
+++ b/doc/bugs/annex_copy_might_not_report_percent-progress_when_it_has_actual_key_file/comment_5_8c33fc01dd1de2abcd3782ff89b437de._comment
@@ -5,4 +5,13 @@
  content="""
 I don't understand what you mean with the find command. Are you talking
 about the "unknown" values in the json?
+
+Oh, I suppose you mean particularly that the bytesize is unknown.
+
+Well, this would make `find` output differ depending on whether the key is
+present or not, in cases where it would otherwise be the same. And it would
+change machine-consumable output in a way that for all I know would break
+stuff.
+
+So, changing that seems like a bad idea.
 """]]