Re: Why we really can't use Facebook for technical discussion.
Phillip Hallam-Baker <phill@hallambaker.com> Sun, 06 June 2021 03:17 UTC
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75933A39C9 for <ietf@ietfa.amsl.com>; Sat, 5 Jun 2021 20:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 nFqF-LeOeba0 for <ietf@ietfa.amsl.com>; Sat, 5 Jun 2021 20:17:21 -0700 (PDT)
Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 554183A39C8 for <ietf@ietf.org>; Sat, 5 Jun 2021 20:17:21 -0700 (PDT)
Received: by mail-yb1-f182.google.com with SMTP id n133so19743310ybf.6 for <ietf@ietf.org>; Sat, 05 Jun 2021 20:17:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Z2DMUgcYkXQsoFx9js9HRoe0vSbXmP1i1LZRlMH+Wdw=; b=TvFlM/u5Lud8Pso3dMKDXUOsqi9CpL0vsVlTEmTAJlqIZdox9TdBLdzflbs+n6Fgwu dCmm6i5qj7AqJcFqqYRriM903dglLiIa+OWNGVjoO+/KSiZ7YVwFo3i4EFRLsKj+w9Wu biE8B14lZ04o+XkrJ6Yom9Cbsi1ti+4oNpDQ5KX3NzAH5mncrbMsfu2NXVXEsBkG6AKX SsSDMRr71kUcbANcAVF6sfcoLYlOKXuaRJYgU1Y/lfes3jXtnsloBrnToigwlAqHHV8T XE7HSOVRAZdBpTsBqAYgRzTZUpspn8PnxXr3C2pMvd7Ey7U9txlLT0Q1X/047U/wqZ3f z1Bw==
X-Gm-Message-State: AOAM532RCyt6CpJfCNdi65nHjr7mviBiZYaflVixJ6JvmpOiaTLH6YfQ axkTdKaXmOgU+eigYdvPmNXvL0dJEFm91i7PID4=
X-Google-Smtp-Source: ABdhPJxzHJa6zSXkfCIyE25q+MnFfqezJmvzwP75EgxO4i47Bhl4L745sAzSkn31KiPwKuXJV3JSfyNTZpTKnBUSZP4=
X-Received: by 2002:a25:f50e:: with SMTP id a14mr15155004ybe.172.1622949440106; Sat, 05 Jun 2021 20:17:20 -0700 (PDT)
MIME-Version: 1.0
References: <HJCFnRF4-BhmmY94naAXr7OwaHttkaKO4_PJx6u2V8ZyHKfo91h0wX96saMVs0sI6KM2vx-h6B-j1dGqj6XqneGrdw-smKRSp9LYfmYZGsg=@softarmor.com> <CALZ3u+a+ry4pd5eAB3QiboA2pwiVhTgc0D4Zte5_u+bj-GsonA@mail.gmail.com> <-Jo05E3w-YIEezoXLI6MpB83ZYosN9BemjreW0cpF-DKiwGfD1pdvjQNWNIRYKnfiqfQR46Ny1e5Ee2ppuMlGTLU1Jei_S4gcB1V9tc6YFI=@softarmor.com>
In-Reply-To: <-Jo05E3w-YIEezoXLI6MpB83ZYosN9BemjreW0cpF-DKiwGfD1pdvjQNWNIRYKnfiqfQR46Ny1e5Ee2ppuMlGTLU1Jei_S4gcB1V9tc6YFI=@softarmor.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 05 Jun 2021 23:17:08 -0400
Message-ID: <CAMm+LwgeZ787ae00+=fw8BP=n5OQ_TMsbtEeG16Zau=5O2Gxrg@mail.gmail.com>
Subject: Re: Why we really can't use Facebook for technical discussion.
To: Dean Willis <dean.willis@softarmor.com>
Cc: ximaera@gmail.com, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ddb6bb05c4105caf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MEIV6atCDrGrSPvwSXwVSb7psDU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jun 2021 03:17:26 -0000
There are multiple problems going on here. One problem that needs urgent attention is a phenomenon I am calling a profile poisoning attack. Facebook does not allow people to say 'this content is garbage, do not show this type of content again'. The only feedback allowed is positive. YouTube and Twitter suffer from the same basic problem but to a lesser degree. Not being able to tell your racist uncle that you have no interest in his bullshit is core to the Facebook brand. It is why it was able to do so much damage. Limiting people to positive feedback sets the stage for a profile poisoning attack. The attacker bombards the target with propaganda knowing that any response from the target will result in the algorithm sending even more propaganda. There is no escape, there is no way to shut the propaganda off. The needs of Facebook advertisers means that the product must not be allowed to say 'stop'. A colleague pointed out that the QAnon slogan is 'do your research' is in effect a clever trap to cause the target to be deluged by more nonsensical conspiracy mongering. It is time to stop this. Dean points out one of the major problems with Facebook - there is only one authority. Only King Zuck gets to decide who can and who cannot speak. His house, his rules. So it is time to make it our house. I have given a lot of thought to this problem over the past two years. I hope folk didn't think I was only thinking about how t do s aslightly better password vault, secure data at rest and do end to end secure messaging. The Mesh was always about an end-to-end secure social media platform. The absolute bare minimum for a social media platform that gives users full control is a name that belongs to them, does not come with an artificial rent, is life-long (except in exceptional circumstances) and can be bound to the service provider(s) of their choice for messaging, social media etc. Mathematical Mesh 3.0 Part VII: Mesh Callsign Service (ietf.org) <https://www.ietf.org/archive/id/draft-hallambaker-mesh-callsign-00.html> There is also a blockchain in there that does not rely on proof of work for stability. The ultimate source of authority and trust for every user is that user themselves. It is kindof a zen thing. The basic code for phase one is passing all relevant unit tests. Just got to write the server config interface. On Sat, Jun 5, 2021 at 8:02 PM Dean Willis <dean.willis@softarmor.com> wrote: > Töma Gavrichenkov < ximaera@gmail.com> wrote: > Peace, > > The thing is, I don't think we've seen a lot of Facebook engineers on the > IETF meetings even before COVID. I'm pretty sure there was someone from > Facebook doing some work around the rtg area, but I fail to recall anyone > else. > > ------ > > Ok, you are probably right. > > But just a few weeks ago, we had a "tools" survey circulating, and several > of the questions related to using assorted social media platforms for IETF > work. > > If you can get banned for a kill -9 comment -- well, we really can't be > using that platform for IETF stuff. Even for jokes, apparently. > > > > >
- Why we really can't use Facebook for technical di… Dean Willis
- Re: Why we really can't use Facebook for technica… Fred Baker
- Re: Why we really can't use Facebook for technica… Töma Gavrichenkov
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Jared Mauch
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Emil Ivov
- Re: Why we really can't use Facebook for technica… Christian Hopps
- Re: Why we really can't use Facebook for technica… Salz, Rich
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Salz, Rich
- Re: Why we really can't use Facebook for technica… Olivier MJ Crépin-Leblond
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Fred Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Spencer Dawkins at IETF
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… lloydwood@users.sourceforge.net
- Re: Why we really can't use Facebook for technica… Bron Gondwana
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Andy Ringsmuth
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Randy Presuhn
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Andy Ringsmuth
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Moderation at scale is hard^Wimpossible, or W… John Levine
- Re: Moderation at scale is hard^Wimpossible, or W… Emil Ivov
- Re: Why we really can't use Facebook for technica… Richard Shockey
- Re: Why we really can't use Facebook for technica… Aqua Q Glass
- Re: Why we really can't use Facebook for technica… Aqua Q Glass
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Lloyd W
- RE: Why we really can't use Facebook for technica… Rob Wilton (rwilton)
- Re: Why we really can't use Facebook for technica… Lloyd W
- RE: Why we really can't use Facebook for technica… Rob Wilton (rwilton)
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: github terms of service, not Why we really ca… John Levine
- The problem we could solve (re github etc.) Phillip Hallam-Baker
- Re: The problem we could solve (re github etc.) John R. Levine
- Re: The problem we could solve (re github etc.) John C Klensin
- Re: The problem we could solve (re github etc.) Michael Richardson
- Re: The problem we could solve (re github etc.) Michael Richardson
- Re: The problem we could solve (re github etc.) Phillip Hallam-Baker
- Re: The problem we could solve (re github etc.) Alessandro Vesely
- Re: The problem we could solve (re github etc.) Phillip Hallam-Baker