diff --git a/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_11_82e32aca2c23a1e27553bcd9708870b2._comment b/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_11_82e32aca2c23a1e27553bcd9708870b2._comment
new file mode 100644
index 0000000000..d236976601
--- /dev/null
+++ b/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_11_82e32aca2c23a1e27553bcd9708870b2._comment
@@ -0,0 +1,25 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 11"""
+ date="2023-07-12T17:03:27Z"
+ content="""
+Please don't engage in unwarranted speculation about strange desires of mine
+to eliminate features that are crucial to git-annex. In general, avoid
+inflammatory language on this website. Thank you.
+
+It's important that git-annex be able to make changes that make it better.
+Backwards compatability is not everything. Improvements can make git-annex
+more cohesive and easier to understand for new users.
+This kind of pre-warned transition is commonly used by git when making
+similarly impactful changes.
+
+annex.synccontent can be set in your global git config. It can also be set
+with `git-annex config` which will affect all clones of that repo. This
+will be a minor amount of work for most users to deal with.
+
+BTW, this transition plan actually started 6 years ago when I added
+annex.syncontent configuration and --no-content.
+[[!commit b77903af48e650dbb777f29e98d0c7b388353ebd]]
+As you note, it's important that's already available in all commonly used
+old versions of git-annex.
+"""]]