Changes between Version 1 and Version 2 of Ticket #2456
- Timestamp:
- 2015-06-15T17:23:05Z (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2456 – Description
v1 v2 1 1 2 For " ``tahoe magic-folder invite COLLECTIVE_WRITECAP NICKNAME``" :2 For "tahoe magic-folder invite '''COLLECTIVE_WRITECAP''' '''NICKNAME'''" : 3 3 4 ( ``COLLECTIVE_WRITECAP`` can, as a special case, be an alias such as ``MAGIC:``.)4 ('''COLLECTIVE_WRITECAP''' can, as a special case, be an alias such as '''MAGIC:'''.) 5 5 6 6 1. Create an empty client DMD. Let its write URI be ``CLIENT_WRITECAP``. 7 2. Diminish ``CLIENT_WRITECAP`` to ``CLIENT_READCAP``, and8 diminish ``COLLECTIVE_WRITECAP`` to ``COLLECTIVE_READCAP``.9 3. Run " ``tahoe ln CLIENT_READCAP COLLECTIVE_WRITECAP/NICKNAME``".10 4. Print " ``COLLECTIVE_READCAP|CLIENT_WRITECAP``" as the invitation,7 2. Diminish '''CLIENT_WRITECAP''' to '''CLIENT_READCAP''', and 8 diminish '''COLLECTIVE_WRITECAP''' to '''COLLECTIVE_READCAP'''. 9 3. Run "tahoe ln '''CLIENT_READCAP''' '''COLLECTIVE_WRITECAP/NICKNAME'''". 10 4. Print "'''COLLECTIVE_READCAP|CLIENT_WRITECAP'''" as the invitation, 11 11 accompanied by instructions on how to accept the invitation and 12 12 the need to send it over a secure channel.