Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?

Matthew Finkel <sysrqb@torproject.org> Sat, 31 July 2021 18:05 UTC

Return-Path: <sysrqb@torproject.org>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A83623A1292 for <111attendees@ietfa.amsl.com>; Sat, 31 Jul 2021 11:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zr0MBMfTjJx3 for <111attendees@ietfa.amsl.com>; Sat, 31 Jul 2021 11:05:29 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D14C23A1290 for <111attendees@ietf.org>; Sat, 31 Jul 2021 11:05:29 -0700 (PDT)
Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4GcXHX42pxzDs9P; Sat, 31 Jul 2021 11:05:28 -0700 (PDT)
X-Riseup-User-ID: E26A1B76008E8730CB062CD0399A4C35491A764674C72402CF03E08C1A5F79AA
Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4GcXHS5P9bz5vbC; Sat, 31 Jul 2021 11:05:24 -0700 (PDT)
Date: Sat, 31 Jul 2021 18:05:17 +0000
From: Matthew Finkel <sysrqb@torproject.org>
To: Carsten Bormann <cabo@tzi.org>, 111attendees@ietf.org
Message-ID: <20210731180517.g2l43erk422w74qo@localhost>
References: <CAED43EF-EA07-4B1F-9826-D2D8F890FB4A@tzi.org> <20210730214914.y4zrqylmn7ynf2cj@localhost> <38B67AAA-0565-4BAE-9ECE-6236C254BF57@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <38B67AAA-0565-4BAE-9ECE-6236C254BF57@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/_9lm0_l6ivgtWqDp16ocbd_xX88>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jul 2021 18:05:35 -0000

On Sat, Jul 31, 2021 at 01:16:30AM +0200, Carsten Bormann wrote:
> On 30. Jul 2021, at 23:49, Matthew Finkel <sysrqb@torproject.org> wrote:
> > 
> > I'm still new around here, so please excuse my ignorance. Are you
> > concerned about malicious edits? Have you seen abuse? Is there an
> > inherent need for edit attribution?
> 
> Much less nefarious — I was taking notes with two other people, and I couldn’t see who they were — a little nudge to authenticate in the browser that you use for note-taking would take this uncertainty away.
> 
> (Why is that important?  If you do shared note taking, you want to know who is distracted, who knows about a particular subject so you can let them write that up, etc.  It’s just harder to fly blind.)

Thanks for explaining the motivation, this is very helpful. I see
authorship of anonymous edits [0][1] should be available in a newer
version, but, from what I can see, a "Guest" can't set their own name .
That is an unfortunate limitation [2].

Requiring being logged-in is an immediate solution, but hopefully [2]
will provide an alternative in the future.

[0] https://github.com/hedgedoc/hedgedoc/issues/505
[1] https://github.com/hedgedoc/react-client/issues/611
[2] https://github.com/hedgedoc/react-client/issues/1411

> 
> The possibility of malicious edits hasn’t hit us yet, and it might, so that may be another reason to go for “logged in” authorization.
> But those really determined to grief would find a way anyway...

Yes, that is certainly a risk, but I encourage supporting
anonymous/pseudonymous contributions and edits because they are
valuable, until this is no longer sustainable.

Thanks,
Matthew

> 
> Grüße, Carsten
> 
> -- 
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees