From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Making GNUS continue to work with Gmail Date: Fri, 14 Aug 2020 12:06:38 +0200 Message-ID: <877du1bky9.fsf@gnus.org> References: <87v9ienz6c.fsf@gnus.org> <878sf9c69y.fsf@gnus.org> <871rkw62t3.fsf@gnus.org> <87bljki71n.fsf@mat.ucm.es> <87364wxlec.fsf@gnus.org> <87imdsgmlw.fsf@mat.ucm.es> <871rkfhkhc.fsf@mat.ucm.es> <875z9p5hnc.fsf@mat.ucm.es> <87mu2y5tr1.fsf@randomsample> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21446"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Emacs developers , Richard Stallman , David De La Harpe Golden To: David Engster Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 14 12:57:34 2020 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 1k6XOv-0005SX-RV for ged-emacs-devel@m.gmane-mx.org; Fri, 14 Aug 2020 12:57:33 +0200 Original-Received: from localhost ([::1]:40734 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k6XOu-0007RN-Ti for ged-emacs-devel@m.gmane-mx.org; Fri, 14 Aug 2020 06:57:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58094) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6Wbp-0005Ud-EW for emacs-devel@gnu.org; Fri, 14 Aug 2020 06:06:49 -0400 Original-Received: from quimby.gnus.org ([2a01:4f9:2b:f0f::2]:57620) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6Wbn-0001ET-H9; Fri, 14 Aug 2020 06:06:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To: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=J1bPwqMBY8L27qwaBm4ZnAdbTrKbpVFMU+yZAKKPkcY=; b=nVQE4UEKw33zH8sj8vpllWHRmh Xj7eforNXnh2eXaqa1hYVjX7JroBHWYBm0TN5Qd30csE8QPuufxKkJxHk7GR8rTOVW4Zb+nH6NSoj tRrqfXm4qubTRPs8buzr3R2Y1YqKxMGon+dJN/3ylu5k5c0BCxL7sbpZymeZCYKurD2o=; Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k6Wbg-0000Z5-JQ; Fri, 14 Aug 2020 12:06:43 +0200 In-Reply-To: <87mu2y5tr1.fsf@randomsample> (David Engster's message of "Thu, 13 Aug 2020 19:40:50 +0200") Received-SPF: pass client-ip=2a01:4f9:2b:f0f::2; envelope-from=larsi@gnus.org; helo=quimby.gnus.org X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. 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, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:253760 Archived-At: David Engster writes: > Yes, they aknowledge this fact. And yet they explicitly forbid embedding > these secrets into (F)OSS applications. See > > https://developers.google.com/terms > > Section 4b, first paragraph. For those that don't like following links: b. Confidential Matters 1 Developer credentials (such as passwords, keys, and client IDs) are intended to be used by you and identify your API Client. You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open source projects. The FSF may, of course, just say "well, we don't care about whatever is in that stupid terms of condition -- we're for free software, and we think these terms are immoral, and so we'll just ignore them (while using the API)". And that'd be fine. But somebody at the FSF would need to register a developer account with Google, in the FSF's name, and get ready to be sued (or billed; Google have a way of saying "well, now you're using this API so much that you have to pay" at random) by Google. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no