Currently, if a device is invited as read-write but acts as if it was read-only (i.e. by responding without a Personal readcap) the magic-folder side ends up returning "wormhole failed or other side declined".
It should have a more-specific error-message (i.e. something about read-only or a protocol-violation or ...)
It could instead allow such a response. That is, allow such a "read-only" response to a read-write invite and "gracefully downgrade" to a read-only participant anyway -- since the "hard work" was producing, relaying and consuming the invite code.
Currently, if a device is invited as
read-writebut acts as if it wasread-only(i.e. by responding without a Personal readcap) the magic-folder side ends up returning "wormhole failed or other side declined".It should have a more-specific error-message (i.e. something about read-only or a protocol-violation or ...)
It could instead allow such a response. That is, allow such a "read-only" response to a read-write invite and "gracefully downgrade" to a read-only participant anyway -- since the "hard work" was producing, relaying and consuming the invite code.