From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Re: oauth2 support for Emacs email clients Date: Sat, 14 Aug 2021 23:04:58 -0400 Message-ID: References: <52589.36892.953561.24840@gargle.gargle.HOWL> <4a9bddb9ec2f05e2e66f@heytings.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4754"; mail-complaints-to="usenet@ciao.gmane.io" Cc: winkler@gnu.org, arthur.miller@live.com, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 15 05:05:53 2021 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 1mF6TB-00011L-Pw for ged-emacs-devel@m.gmane-mx.org; Sun, 15 Aug 2021 05:05:53 +0200 Original-Received: from localhost ([::1]:54870 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mF6TA-0008Ht-8z for ged-emacs-devel@m.gmane-mx.org; Sat, 14 Aug 2021 23:05:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46606) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mF6SK-0007az-K4 for emacs-devel@gnu.org; Sat, 14 Aug 2021 23:05:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38676) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mF6SI-0006TY-VU; Sat, 14 Aug 2021 23:04:58 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1mF6SI-0001EC-OX; Sat, 14 Aug 2021 23:04:58 -0400 In-Reply-To: <4a9bddb9ec2f05e2e66f@heytings.org> (message from Gregory Heytings on Sat, 14 Aug 2021 11:12:53 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:272398 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Can someoe point me at the _precise_ agreement text for this? Then the > > FSF could actually study the question. Thanks for sending them. > 4.a.1: "When using the APIs, you may not (or allow those acting on your > behalf to) [s]ublicense an API for use by a third party. Consequently, you > will not create an API Client that functions substantially the same as the > APIs and offer it for use by third parties." I am not sure concretely what this is talking about. Does the FSF ever do anything remotely like "sublicense an API"? I don't think so, but I can't be really sure until I know what it would mean. Also, what is "an API Client that functions substantially the same as the APIs"? You seem to believe that movemail fits those words, but I doubt it. I don't know what that API can do, but I would expect it includes a lot more funtionality than just "download all the incoming mail as an inbox file and delete it on the server." However, supposing that extending a program to "download all the incoming mail as an inbox file and delete it on the server" did fall under that description, I see nothing to stop us from doing it. Any free license permits adding features, and some of us have never agreed to these Google terms. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)