From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Sun, 15 May 2022 07:04:55 +0200 Message-ID: References: <877d72nf3h.fsf@gmail.com> <87v8ul4ad4.fsf@gmail.com> <87r157qcta.fsf@logand.com> <87wneyc6zu.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sS31Y0EauuTAi8N3" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2865"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 15 07:07:59 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nq6U2-0000c8-TC for ged-emacs-devel@m.gmane-mx.org; Sun, 15 May 2022 07:07:58 +0200 Original-Received: from localhost ([::1]:42594 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nq6U1-0003Dx-U9 for ged-emacs-devel@m.gmane-mx.org; Sun, 15 May 2022 01:07:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45208) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nq6RB-0008CD-JE for emacs-devel@gnu.org; Sun, 15 May 2022 01:05:03 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:59840) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nq6R9-000862-6l for emacs-devel@gnu.org; Sun, 15 May 2022 01:05:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=hqoOEAyj6TZSdf4+dHl9HUzy97vQ0N3lSP/MGd02fM8=; b=Focskw3+geo03gMAdr9VHNodl8 U9MVpbCpoW7ATsUKsG7nTok4lgEzStet+AyhedefOnvPwez+UvWtLSQopf0wd9FTKN0i3/0p/rueL t/Euy++lTSah6j6/Db7hx5wevoFo9lbbxUAF2xLGk2Eh6EXNCTSI1uHMxBZs5WgTzF8E1zeDxfMlT emAnjJbkahnSQubkD6URc2T/hgNflwQEZidpXZObSKyo3rKOF99Lw79wIlGk6CSWAatTtOajMfvSI VAEADksAsi7Ox18yvYflpdVeM4olvmqZbypyJPDoVJCDO81cePaeW4aPFbQH0QL7z6FwZEod37DnB q0iqqCLQ==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1nq6R5-0003rP-3Q for emacs-devel@gnu.org; Sun, 15 May 2022 07:04:55 +0200 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289789 Archived-At: --sS31Y0EauuTAi8N3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 14, 2022 at 05:43:33PM -0400, chad wrote: > There is a small additional wrinkle to Tim Cross' excellent summary: > [about uncertainty] I'm > a firm proponent of Hanlon's Razor, but it's hard to believe that this > outcome isn't at least tacitly accepted. I've vented my opinion several times here, so I fear I'm repeating myself. I think bigcorps have, to some extent, given up on controlling [0] users via proprietary software. Free software has won, in some strange way (a bit like the Monkey's Paw [1], returning as Open Source). To protect their business model, they have to devise other ways. One of them is to interpose themselves as monopolistic "services" between people and their everyday tasks: information retrieval (Google), communications (Facebook, Twitter et al), business contact (Google, Microsoft, etc.), mobile connectivity (Google, Apple), marketplace (Amazon)... I could go on. What we are seeing here is the "service" of identity management, something up to now reserved to nation states (they used to issue passports, remember?) Now I'm coming back to you, Chad: as long as they are trying to conquer market share, this kind of uncertainty is useful: they get the "cheaters", i.e. those who are disgusted by the very concept. Currently those Firefox users. They formally break the T&C, but we don't go after them... yet. To offer a historical parallel: I remember a time (must have been around Windows 3.x) where everyone knew that using a number divisible by seven [2] gave you a valid Windows license key, so you could install an illegal copy. I'm convinced that back then, Microsoft /wanted/ to see its user base extended by this huge population. They weren't going to pay anyway, they were those trained in Windows advocating for it at work, they could be cracked on at will, and oh, the complaining about those "criminals" "stealing" billions and billions "worth" of software. What's not to like? I don't believe Hanlon applied then. I don't believe Hanlon applies here (that's why I came up with this mix of Hanlon's razor and Clarke's Third). Cheers [0] Control sounds sooo... evil. It's just about business, crisp and cold. [1] https://en.wikipedia.org/wiki/The_Monkey%27s_Paw [2] the concrete details may be wrong: it's a while ago --=20 t --sS31Y0EauuTAi8N3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCYoCJ8AAKCRAFyCz1etHa RkyfAJ4odvrIMRL7fe/4cPvVHI8bEvE2BwCePTFtXSOL1mUZy3xvVdCW5FjAfkA= =Mk9o -----END PGP SIGNATURE----- --sS31Y0EauuTAi8N3--