IETF Logo Mail Archive

Re: Old directions in social media.

"Salz, Rich" <rsalz@akamai.com> Tue, 05 January 2021 21:24 UTC

Return-Path: <rsalz@akamai.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 A85B73A03F1 for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 13:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 8kTa8hysSreF for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 13:24:39 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 657303A03F4 for <ietf@ietf.org>; Tue, 5 Jan 2021 13:24:39 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 105L9Crb010068; Tue, 5 Jan 2021 21:24:38 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=SNTbsIZtwj2aWqLtg9/i2uVKXN2fsRqWQptHVi2b74w=; b=HZnGDQxCKNoMbTZkmrcIpBWbcH7pThOAw+NUj5GR+fGUj66GhgvIjwXukp2CuO96ujBD qJYs+IsCL8baw/eIDVVlOS4T/3CCYmUIFwCfz7qY0r5JmUOVtSzn+8DWhBrI5g1Y/P1/ L72QlrnTn6mXHniAy7oEjr11LlCTPCgkOxB/mVfT78JWs+5YaavXFdvn9ouChLCrhcry zBDgWTVt//4STwzQ9Dq8rbTakVSaD82MIEG+FZ8ONXY52efyPe3Gvj4iXD+VU2GNdMAQ 9kJaUYpLG3BhVO1WQmCfNQsTcO0DaVLodaCpkeIX+LW9yBbgi6/Q+WM03aP8MNNIzXm4 bg==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 35thru7mb5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 05 Jan 2021 21:24:38 +0000
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 105L6pcE023091; Tue, 5 Jan 2021 13:24:37 -0800
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint5.akamai.com with ESMTP id 35tqpey869-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 05 Jan 2021 13:24:37 -0800
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 Jan 2021 16:24:36 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.010; Tue, 5 Jan 2021 16:24:36 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Keith Moore <moore@network-heretics.com>, Kyle Rose <krose@krose.org>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Old directions in social media.
Thread-Topic: Old directions in social media.
Thread-Index: AQHW4sDa9Z9oIo3c5U6o2YL/AuVt06oZkesAgAAHGoCAAANcAIAAA0kAgAAJTAD//8AWgIAAZdeA//+98AA=
Date: Tue, 05 Jan 2021 21:24:36 +0000
Message-ID: <CA7629F5-4DF0-4C34-92CB-A346D7ED4C1F@akamai.com>
References: <CAJU8_nUostFKjKU43wk-RG5+8SYgMc8Ag-MWs=UXi7x8YXTaKA@mail.gmail.com> <D152D8C5-1863-4BEE-9DA4-A1C31AAC809C@network-heretics.com> <47B4988E-5865-40FF-93C4-9E7D1A63C074@akamai.com> <2353617a-2a45-9143-9529-dac1cc16634e@network-heretics.com>
In-Reply-To: <2353617a-2a45-9143-9529-dac1cc16634e@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.44.20121301
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_CA7629F54DF04C3492CBA346D7ED4C1Fakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-05_07:2021-01-05, 2021-01-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 spamscore=0 phishscore=0 malwarescore=0 suspectscore=0 mlxlogscore=757 bulkscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101050124
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2021-01-05_07:2021-01-05, 2021-01-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 priorityscore=1501 mlxscore=0 lowpriorityscore=0 suspectscore=0 malwarescore=0 spamscore=0 phishscore=0 clxscore=1015 mlxlogscore=661 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101050124
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.60) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x9SQY7egEolw5RdtIbW1XU-D6Iw>
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: Tue, 05 Jan 2021 21:24:41 -0000

  *   Yes, and now we have enough experience with this experiment to know what was good and what was bad about it.   So let's learn from our experience and make adjustments based on that experience.  Instead of trying to cripple IETF.

Strongly disagree.  But for those writing the report, here’s some anecdata: The HTTPAPI working group would be ineffective if it weren’t working on GitHub. Looking at the membership list, we have key players from all sorts of HTTP API frameworks.


  *   p.s. I consider your message personally insulting and therefore inappropriate for IETF.

Sorry you feel that way; I was commenting on the discussion.

v2.23.0 | Report a Bug | By Email