diff --git a/doc/bugs/p2phttp__58___drop_difference_wideopen_unauth-readonly/comment_2_be1f58d6c49a69ddae692cef911245be._comment b/doc/bugs/p2phttp__58___drop_difference_wideopen_unauth-readonly/comment_2_be1f58d6c49a69ddae692cef911245be._comment
new file mode 100644
index 0000000000..0d552e4b63
--- /dev/null
+++ b/doc/bugs/p2phttp__58___drop_difference_wideopen_unauth-readonly/comment_2_be1f58d6c49a69ddae692cef911245be._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="matrss"
+ avatar="http://cdn.libravatar.org/avatar/59541f50d845e5f81aff06e88a38b9de"
+ subject="comment 2"
+ date="2024-10-14T12:01:40Z"
+ content="""
+I've solved my issue in forgejo-aneksajo by special-casing the lockcontent endpoint to return a 403 for unauthorized requests, instead of a 401 like all other POST endpoints (put, remove, etc.). I presume that this is also what `git annex p2phttp` itself does, is that right? Maybe the specific response expected by git-annex in case of an unauthorized requests could be part of the protocol specification...
+"""]]
diff --git a/doc/todo/p2phttp__58___regularly_re-check_for_annex.url_config/comment_1_425320fa7afe8a9f16c7fa0af924e014._comment b/doc/todo/p2phttp__58___regularly_re-check_for_annex.url_config/comment_1_425320fa7afe8a9f16c7fa0af924e014._comment
new file mode 100644
index 0000000000..728b5ea046
--- /dev/null
+++ b/doc/todo/p2phttp__58___regularly_re-check_for_annex.url_config/comment_1_425320fa7afe8a9f16c7fa0af924e014._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="matrss"
+ avatar="http://cdn.libravatar.org/avatar/59541f50d845e5f81aff06e88a38b9de"
+ subject="comment 1"
+ date="2024-10-14T12:21:54Z"
+ content="""
+It seems like I can make git-annex discover a newly added `annex.url` setting by unsetting `remote.<name>.annex-uuid` and then doing `git annex init` again or trying to copy something to the remote.
+"""]]