Added a comment
authormsz <msz@web>
Thu, 10 Apr 2025 16:56:50 +0000 (16:56 +0000)
committeradmin <admin@branchable.com>
Thu, 10 Apr 2025 16:56:50 +0000 (16:56 +0000)
doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_5_e3c67afcb36ba91a31de740b3dd02ba3._comment [new file with mode: 0644]

diff --git a/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_5_e3c67afcb36ba91a31de740b3dd02ba3._comment b/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_5_e3c67afcb36ba91a31de740b3dd02ba3._comment
new file mode 100644 (file)
index 0000000..7e7383d
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="msz"
+ avatar="http://cdn.libravatar.org/avatar/6e8b88e7c70d86f4cfd27d450958aed4"
+ subject="comment 5"
+ date="2025-04-10T16:56:50Z"
+ content="""
+Thank you, this is very informative!
+
+Could such a special remote use the same \"transport\" as the underlying remote (thinking of p2p http in particular), which would mean the same authentication & the same set of permissions server side?
+"""]]