comment
This commit is contained in:
parent
5c9a6af5f8
commit
c5b0ca8982
2 changed files with 10 additions and 1 deletions
|
@ -1,6 +1,6 @@
|
||||||
[[!comment format=mdwn
|
[[!comment format=mdwn
|
||||||
username="joey"
|
username="joey"
|
||||||
subject="""comment 5"""
|
subject="""comment 6"""
|
||||||
date="2025-04-11T17:20:08Z"
|
date="2025-04-11T17:20:08Z"
|
||||||
content="""
|
content="""
|
||||||
Implemented this as the mask special remote.
|
Implemented this as the mask special remote.
|
|
@ -0,0 +1,9 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 7"""
|
||||||
|
date="2025-04-11T17:23:59Z"
|
||||||
|
content="""
|
||||||
|
> 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?
|
||||||
|
|
||||||
|
Yes, the underlying remote is used as-is, whatever it is.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue