[Din] Re: Fwd: New Version Notification for draft-mcfadden-consolidation-taxonomy-05.txt
bumblefudge von CASA <bumblefudge@learningproof.xyz> Thu, 07 November 2024 09:27 UTC
Return-Path: <bumblefudge@learningproof.xyz>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E278C151089 for <din@ietfa.amsl.com>; Thu, 7 Nov 2024 01:27:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVlRLeEyOgHe for <din@ietfa.amsl.com>; Thu, 7 Nov 2024 01:27:00 -0800 (PST)
Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E460C151543 for <din@irtf.org>; Thu, 7 Nov 2024 01:27:00 -0800 (PST)
Date: Thu, 07 Nov 2024 09:26:54 +0000
To: "jens@interpeer.org" <jens@interpeer.org>, "din@irtf.org" <din@irtf.org>, "mark@internetpolicyadvisors.com" <mark@internetpolicyadvisors.com>
From: bumblefudge von CASA <bumblefudge@learningproof.xyz>
Message-ID: <sH-E51mDA1q3Iyn6hGDlRaeCtkIDn9qPvapKlS9MOi7sHqbXO0N-TjwT6A3yYp_9UIL7sQgTAwC8ScGDCLaV-abqHzz_hlOhj9NCpVpPUQM=@learningproof.xyz>
In-Reply-To: <1209439777.38099.1730923797027@fidget.co-bxl>
References: <172934455654.1662159.7118294925011276787@dt-datatracker-78dc5ccf94-w8wgc> <CAJMFcSeaoswp-i1fgxht5r=1rvNntpxks9ZUxtR6Mb=LXpGUsg@mail.gmail.com> <1209439777.38099.1730923797027@fidget.co-bxl>
Feedback-ID: 85909410:user:proton
X-Pm-Message-ID: d32156a3b205873e8c16ad0a981b7ec4cc3e1ba0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1=_EwNv0la69oz3OEl3o8we3fwo4lAa8cSNIOq0xVV3YW0"
Message-ID-Hash: COWPHY5PJ6VAMSQUY5QHHEKDUEKKY6LW
X-Message-ID-Hash: COWPHY5PJ6VAMSQUY5QHHEKDUEKKY6LW
X-MailFrom: bumblefudge@learningproof.xyz
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-din.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Din] Re: Fwd: New Version Notification for draft-mcfadden-consolidation-taxonomy-05.txt
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/Lxzs9fwis5hMtz5vVbv1yyLSJa0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Owner: <mailto:din-owner@irtf.org>
List-Post: <mailto:din@irtf.org>
List-Subscribe: <mailto:din-join@irtf.org>
List-Unsubscribe: <mailto:din-leave@irtf.org>
Going on record as owing a deep textual review --- bumblefudge janitor @Chain Agnostic Standards Alliance contractable via learningProof UG mostly berlin-based Sent from Proton Mail Android -------- Original Message -------- On 11/6/24 8:09 PM, Jens Finkhäuser wrote: > Hi all, > > I feel bad for not having participated in the conversation leading up to this year's DINRG, in particular because I really like this work and the related draft on consolidation effects. > > I need to reiterate, of course, that this is purely based on what was being presented. I need to read and comment on the drafts in a lot more detail. > > However, just to get some conversation started: > > - It may be worth talking to HRPC. It's not that they have much to say on the topic of consolidation/centralization in principle. That said a number of the protocol considerations they mention in RFC9620 relate to human rights violations that are enabled by power imbalances in the digital systems humans use. Section 4.19 is explicitly about this topic ( https://www.rfc-editor.org/rfc/rfc9620.html#name-decentralization ), but e.g. the section on censorship resistance is particularly relevant due to the effective power platform providers have in more centralized systems. I suspect referencing such relationships in that RFC in the effects draft could strengthen the argument that it is not so much economic but power incentives that drive centralization. > > I understand the argument that money is power and power makes money (TL;DR), but the counter argument to this is that money is the means by which power is exercised and its distribution controlled. The underlying principle of the two then cannot be the means. > - I spoke to Mark briefly after the session to highlight that there are also various conversations going on about "digital sovereignty", "public digital goods" and a "digital commons". They are not interchangeable, but closely related. Also, they are political terms related to similar concerns we've discussed today at the more technical level. > > The differentiation between a public digital good and the digital commons is a little too subtle to go into here IMHO, but a "commons" is fundamentally a distributed/decentralized thing. The concept exists and has existed for ages, and is a tool for leveling the playing field between those with more vs. less means. One of the ongoing battles throughout history is to prevent those with more means to also exploit the commons more, because that is counter to its intent. > > On the other hand, sovereignty (digital or otherwise) is about retaining power for self-determination, and not handing this to someone else. It does not necessarily imply that many people hand power to a central entity, but that's of course a possibility. So the relationship between that term and centralization of power should be understandable. > - There is a consideration IMHO missing from the taxonomy draft (which, again, I skimmed over only briefly just now), which one might want to call "algorithmic centralization". The specific issue here lies with the use of large language models, but also similar technology, to a) train on available (human or organically generated, etc.) data, and b) then synthesize a lot more data that is sufficiently indistinguishable from its source to effectively control the discoverability of the original source data. > > There are arguments to be made that this is a subset of application/service consolidation. It's also arguable that this is less about the service or application, because what troll farms (disinformation generators) have successfully shown is that you do not need to run a service to control narratives; you need only to flood other services with disinformation. > > Another argument can be made that there is a distinction between what is being generated (data consolidation) and how it is being generated (algorithmic consolidation). The use of algorithms here yields a significantly higher return on investment in terms of achieving leverage over the data space than could be gained by traditional means. Note that this, too, overlaps with HRPCs concerns about "negative impact" as mentioned in their section 4.21. > > As it so happens, today the author Charles Stross happened to complain about this very thing: https://wandering.shop/@cstross/113436422346204178 > "In 20/20 hindsight, I should have paid more attention to the drop in traffic to my blog (both views and comments posted) since January 2024, and noted Google's de-emphasizing blogs in favour of extruded text product, and realized: if you suppress public speech via small private media (blogs) you're implicitly boosting the reach of centrally controlled platforms. > > This is censorship with American characteristics. > > The fix, as they say, is in." > > None of these remarks are meant to be final or replace a deeper review and/or text suggestions. It's more that I wanted to show my appreciation for the effort put into the drafts by (hopefully) sparking some discussion. > Jens > > On Oct 21, 2024 at 5:30 PM, Mark McFadden <mark@internetpolicyadvisors.com> wrote: > >> A new version of Internet-Draft draft-mcfadden-consolidation-taxonomy-05.txt >> has been successfully submitted by Mark McFadden and posted to the >> IETF repository. >> >> Name: draft-mcfadden-consolidation-taxonomy >> Revision: 05 >> Title: A Taxonomy of Internet Consolidation >> Date: 2024-10-19 >> Group: Individual Submission >> Pages: 16 >> URL: https://www.ietf.org/archive/id/draft-mcfadden-consolidation-taxonomy-05.txt >> Status: https://datatracker.ietf.org/doc/draft-mcfadden-consolidation-taxonomy/ >> HTML: https://www.ietf.org/archive/id/draft-mcfadden-consolidation-taxonomy-05.html >> HTMLized: https://datatracker.ietf.org/doc/html/draft-mcfadden-consolidation-taxonomy >> Diff: https://author-tools.ietf.org/iddiff?url2=draft-mcfadden-consolidation-taxonomy-05 >> >> Abstract: >> >> This document contributes to the ongoing discussion surrounding >> Internet consolidation. At recent IETF meetings discussions about >> Internet consolidation revealed that different perspectives gave >> completely different views of what consolidation means. While we use >> the term consolidation to refer to the process of increasing control >> over Internet infrastructure and services by a small set of >> organizations, it is clear that that control is expressed through >> economic, network traffic and protocol concerns. As a contribution >> to the discussion surrounding consolidation, this document attempts >> to provide a taxonomy of Internet consolidation with the goal of >> adding clarity to a complex discussion. >> >> The IETF Secretariat >> >> _______________________________________________ >> >> Din mailing list -- >> din@irtf.org >> >> To unsubscribe send an email to >> din-leave@irtf.org
- [Din] Fwd: New Version Notification for draft-mcf… Mark McFadden
- [Din] Re: Fwd: New Version Notification for draft… Jens Finkhäuser
- [Din] Re: Fwd: New Version Notification for draft… bumblefudge von CASA
- [Din] Re: Fwd: New Version Notification for draft… William Lehr