Marc Nieper-Wißkirchen <
marc....@gmail.com> writes:
> Am So., 13. März 2022 um 00:03 Uhr schrieb John Cowan <
co...@ccil.org>:
>>
>>
>>
>> On Sat, Mar 12, 2022 at 5:43 PM Dr. Arne Babenhauserheide <
arne...@web.de> wrote:
>>
>>>
>>> The main advantage is that this is encrypted with the clientside key, so
>>> there is no sensitive data on the server and it is easy to create small
>>> breakout documents in a limited group that are then only accessible in
>>> that group (and not available from the server).
>>
>> Can you explain why you want to do standards development in secret?
>> Ethical issues aside, if the key is lost, part of the history of the
>> development of the standard becomes permanently inaccessible.
This is for live-collecting, not for storage. After the interactive
discussion, export it and posts it to the email list.
Would you want to store every accidental paste in public?
> Let me add that it is part of my wishlist proposal to copy the
> document to this list making it part of the history. Think of it like
> people meeting in a room collecting R7RS Large wishes and publishing
> the collection at the end of their meeting.
That’s what I mean, yes.
In a real-world discussion there is the option to say “please keep this
out of the protocol; I did not mean it like that and people will
misinterpret it”.
If you discuss interactively in public, you lose that — and people
self-censor.
Look at how easy my argument for privacy-preserving discussion-platforms
can be misinterpreted as wanting to discuss in secret.
Think of it like a break-out room. In the EU parliament there is a mode
of discussion in export meetings where everything is OK to be quoted,
but without naming the person who said it.
During the discussion you need to know who said what and when, but
afterwards that might be problematic.
> In any case, the meeting should be open as the process here so far, so
> a globally accessible document would be fine. I understand that not
> all people would want to use non-free software, so Google Docs may be
> out.
>
> Arne, can you set up a cryptpad document that is accessible by
> everyone (possibly after posting a key on this list)?
Yes. Once the link is posted, it is public: The key is in the link.
For example this one is public (now):
https://cryptpad.digitalcourage.de/code/#/2/code/edit/1ihOWsqkz+np7YViV-SwCcnM/
But here the history is also public. For interactive discussions I’d
rather export from this after the discussion and post it here — or
import the export into a new pad.