diff --git a/doc/todo/Read-only_support_for_webdav/comment_2_968e09a53e4d583c67dea328d00930b4._comment b/doc/todo/Read-only_support_for_webdav/comment_2_968e09a53e4d583c67dea328d00930b4._comment
new file mode 100644
index 0000000000..ca1a0408ce
--- /dev/null
+++ b/doc/todo/Read-only_support_for_webdav/comment_2_968e09a53e4d583c67dea328d00930b4._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="msz"
+ avatar="http://cdn.libravatar.org/avatar/6e8b88e7c70d86f4cfd27d450958aed4"
+ subject="comment 2"
+ date="2025-03-05T11:27:38Z"
+ content="""
+Thank you! I had an opportunity to try it out only recently, and it worked great!
+
+With that, I can use a regular (read/write) WebDAV special remote to store data on a Nextcloud instance; then, when I want to publish (without granting write access), I can `initremote --sameas`, and enable the second remote using a public read-only WebDAV URL (which is not the share link generated by Nextcloud, but can be easily derived from it). The public share can be password-protected. And, indeed, git-remote-annex works seamlessly on top. Very little needs to be done in terms of remote configuration to make it work. This is cool.
+"""]]