Re: [hrpc] draft-irtf-hrpc-association-02

Stéphane Couture <listes@stephcouture.info> Fri, 17 May 2019 15:21 UTC

Return-Path: <listes@stephcouture.info>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DC5120110 for <hrpc@ietfa.amsl.com>; Fri, 17 May 2019 08:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 JEHiDl0UydAP for <hrpc@ietfa.amsl.com>; Fri, 17 May 2019 08:21:52 -0700 (PDT)
Received: from homere.koumbit.net (homere.koumbit.net [199.58.80.81]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F246A120198 for <hrpc@irtf.org>; Fri, 17 May 2019 08:21:42 -0700 (PDT)
Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: steph@stephcouture.info) by homere.koumbit.net (Postfix) with ESMTPSA id A2D1D1E425DD for <hrpc@irtf.org>; Fri, 17 May 2019 11:21:41 -0400 (EDT)
Received: by mail-wr1-f49.google.com with SMTP id d9so7614979wrx.0 for <hrpc@irtf.org>; Fri, 17 May 2019 08:21:40 -0700 (PDT)
X-Gm-Message-State: APjAAAXGAcyDvvDRIsXyNX1H5e5zVeaboMNqaIl3hFlu+HJRxKJyhOnB OodAM0sS/dqrZKPrFrBafeNGcsYMptXK8/hnZ8Q=
X-Google-Smtp-Source: APXvYqwHhwCVJa7GSpG0uuuqB9u+G1EjQ28RvZYYCHw6G4e4SOHq/ZNoBlJnJMHvlk0tyyxm1cOw4n3DEmhk4te6yuo=
X-Received: by 2002:adf:db82:: with SMTP id u2mr33538119wri.316.1558106499948; Fri, 17 May 2019 08:21:39 -0700 (PDT)
MIME-Version: 1.0
References: <e91dd252-6fcc-41c5-9077-b3934ddba7ea@avris-iPad> <CABtrr-U76xGXjiKW+DgpVkGU27B2Gb7YpZW-vBOSq-_R2XZRng@mail.gmail.com> <27c2964d-e533-9ea3-bacf-763afe9111ee@nielstenoever.net> <9b24f9c1-c8dc-16e2-ce3d-e1749828ddab@doria.org> <CABtrr-VK4ndYsS2990AmySwNSKjBbxBKLvk5hiAq4mp=8r=6-w@mail.gmail.com> <dad6b90a-dc88-3de3-2e8f-4981a279b86a@apc.org> <CANZrNV_w3gL0sPQO-9uF=gWthSLg4L8Q9U5=nyV1tTMAdy49Xw@mail.gmail.com> <563cc37d-eac1-1b20-bdb4-86a0dcd5e73d@apc.org>
In-Reply-To: <563cc37d-eac1-1b20-bdb4-86a0dcd5e73d@apc.org>
From: Stéphane Couture <listes@stephcouture.info>
Date: Fri, 17 May 2019 11:21:28 -0400
X-Gmail-Original-Message-ID: <CANZrNV_MZTpu+pUXkveGsyq0wLCt9hMi7b=7R6MA_5L5yJznsw@mail.gmail.com>
Message-ID: <CANZrNV_MZTpu+pUXkveGsyq0wLCt9hMi7b=7R6MA_5L5yJznsw@mail.gmail.com>
To: avri doria <avri@apc.org>
Cc: Stéphane Couture <listes@stephcouture.info>, Joseph Lorenzo Hall <joe@cdt.org>, hrpc@irtf.org
Content-Type: multipart/alternative; boundary="00000000000073a9a2058916f090"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/OKp-QI_Z-Lij61bp5uJIZQig798>
Subject: Re: [hrpc] draft-irtf-hrpc-association-02
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 15:21:54 -0000

Hi all,


So, as I mentioned in my last email, I re-read the document and am now
sharing some comments. Forgive me if my style is too academic.


1. As it was mentioned earlier (by Avri I think), I think the stated goal
of the document to "establish the causal link" is too strong. The notion of
"causality" usually refers to a quantitative approach (for instance using
regression analysis). The analysis provided in this document is in my view
fundamentally qualitative, and I do not see how it can support a strong
claim of causality. I also have to say that I come from the field of
Science and Technology Studies, where causal relationships have been
strongly debunked in favor of more complex relationships, so I am a bit
doubtful about the term here.


2. The document is also saying that RFC8280, "established either causal or
deterministic relationships,” but I don't see mention of "causal" in
RFC820, but maybe I am wrong here.


3. There are many places we go too quickly from "machine communication" to
"human communication,” and from "computing interoperability" to "human
association.” For instance, at the end of the paper, it is written that
"This lack of interoperation is harming the ability of people to set or
negotiate their own terms on which they would like to assemble or
associate.” However, many authors (and activists) are still praising
proprietary social media for their capacity to facilitate assembly and
collective action. And on the other hand, more interoperable platforms
sometime lack user-friendliness or a wider user base to allow a wide range
of people to participate. So, there might be other variables than
"interoperability" to take into account to see how technologies facilitate
association.


On this, I think the last sentence should be unfolded :


"The use of social-media platforms has enabled groups to associate, but it
has also rendered users unable to change platforms, therefore leading to a
sort of “forced association” that inhibits people to fully exercise their
freedom of assembly and association.”


What is a "forced association" ? Why is the inability to change platforms
necessarily "leading" to "forced association" ? If there is a causal link
to be made, I would think it is here.


4. Concerning the flow of the argument, it would be good to explain how, or
why, each of these cases were chosen. It is stated that a "purposive
sampling approach, aimed at the typicality and paradigmatic nature of the
cases" was chosen, but I think there would be a need for better explanation
on the "typicality and paradigmatic nature" of each of the cases.


5. Again, on the flow of the argument, it would be good to add a sentence
at the end of each of the cases to explain how it is related to freedom of
association. For many of them, we have to guess it.


I also made some more specific comments in the document that I could share
for the rewriting the new version.


Best,


Stéphane



Le jeu. 16 mai 2019 à 11:36, avri doria <avri@apc.org> a écrit :

> Hi,
>
> I think that sounds splendid.
>
> To both of you, please let Mallory and me know how we can help.
>
> thanks
>
> avri
>
>
> On 16-May-19 11:05, Stéphane Couture wrote:
> > Hi all,
> >
> > Mallory have asked me recently to act as editor, as way to contribute
> > to the group. I was hesitant to do it alone, but I'd be happy to be
> > "co-traveler" on this, if Joseph and others agree.
> >
> > I also made comments on the draft, but for some reasons, my document
> > didn't save, so I need to write them again. I'll send them asap.
> >
> > Best,
> >
> > Stéphane
> >
> > Le jeu. 16 mai 2019 à 10:50, avri doria <avri@apc.org
> > <mailto:avri@apc.org>> a écrit :
> >
> >     Hi,
> >
> >     Thank you.
> >
> >     Any takers on the role of co-traveler?
> >
> >     thanks
> >
> >     avri
> >
> >
> >     On 16-May-19 09:19, Joseph Lorenzo Hall wrote:
> >     > I'm definitely interested in helping incorporate the flurry of
> >     > feedback this draft received before IETF 104. I would love a
> >     > co-traveler...
> >     >
> >     > On Sun, Mar 31, 2019 at 4:39 PM <avri@doria.org
> >     <mailto:avri@doria.org>
> >     > <mailto:avri@doria.org <mailto:avri@doria.org>>> wrote:
> >     >
> >     >     Hi,
> >     >
> >     >     Thanks to you and to Gisela for taking the draft as far as
> >     it has
> >     >     come.
> >     >
> >     >     Mallory and I will discuss how best to continue with this
> >     draft.
> >     >     Definitely interested in hearing from anyone who is
> >     interested in
> >     >     being
> >     >     part of an editorial effort to take it toward completion.
> >     >
> >     >     Thanks
> >     >
> >     >     avri
> >     >
> >     >
> >     >     On 28-Mar-19 13:36, Niels ten Oever wrote:
> >     >     > Thanks for all the great reviews and comments. It is great to
> >     >     see a lot of new energy on this draft.
> >     >     >
> >     >     > As mentioned, Gisela and I feel like we are not the best
> >     persons
> >     >     to integrate the proposed changes, so we would like to take
> >     a step
> >     >     back a lead authors and hope that others will step forward
> >     to take
> >     >     the lead to take this RG document further.
> >     >     >
> >     >     > If there are no others who want to work as co-authors,
> perhaps
> >     >     the reviewers (and RG participants and others) could propose
> >     >     alternate text either in attached markdown document, or as pull
> >     >     requests on github (
> >     >
> >
> https://github.com/IRTF-HRPC/drafts/blob/master/draft-association.md
> >     >     )?
> >     >     >
> >     >     > Thanks in advance,
> >     >     >
> >     >     > Niels and Gisela
> >     >     >
> >     >     >
> >     >
> >     >     _______________________________________________
> >     >     hrpc mailing list
> >     >     hrpc@irtf.org <mailto:hrpc@irtf.org> <mailto:hrpc@irtf.org
> >     <mailto:hrpc@irtf.org>>
> >     >     https://www.irtf.org/mailman/listinfo/hrpc
> >     >
> >     >
> >     >
> >     > --
> >     > Joseph Lorenzo Hall
> >     > Chief Technologist, Center for Democracy & Technology
> >     > [https://www..cdt.org <http://cdt.org> <https://www.cdt.org>]
> >     > 1401 K ST NW STE 200, Washington DC 20005-3497
> >     > e: joe@cdt.org <mailto:joe@cdt.org> <mailto:joe@cdt.org
> >     <mailto:joe@cdt.org>>, p: 202.407.8825, pgp:
> >     > https://josephhall.org/gpg-key
> >     > Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
> >     >
> >     >
> >     > _______________________________________________
> >     > hrpc mailing list
> >     > hrpc@irtf.org <mailto:hrpc@irtf.org>
> >     > https://www.irtf.org/mailman/listinfo/hrpc
> >
> >     _______________________________________________
> >     hrpc mailing list
> >     hrpc@irtf.org <mailto:hrpc@irtf.org>
> >     https://www.irtf.org/mailman/listinfo/hrpc
> >
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>