[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gmail+imap+smtp (oauth2)
From: |
Tomas Hlavaty |
Subject: |
Re: gmail+imap+smtp (oauth2) |
Date: |
Fri, 06 May 2022 18:41:40 +0200 |
On Fri 06 May 2022 at 07:38, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Problem is, Google T&C require that the application ID is kept secret.
>> For open source, this is a problem because we cannot add the applicaiton
>> ID and keep it secret while making the code open source.
> FWIW, it's also a problem for proprietary applications since the secret
> will necessarily be somewhere inside the executable as well.
it is not a problem for proprietary services
- Re: gmail+imap+smtp (oauth2), (continued)
- Re: gmail+imap+smtp (oauth2), Tim Cross, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Eric S Fraga, 2022/05/06
- Re: gmail+imap+smtp (oauth2), tomas, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Tim Cross, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Tomas Hlavaty, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Tim Cross, 2022/05/06
- Re: gmail+imap+smtp (oauth2),
Tomas Hlavaty <=
- Re: gmail+imap+smtp (oauth2), Tomas Hlavaty, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Tim Cross, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Stefan Monnier, 2022/05/06
- Re: gmail+imap+smtp (oauth2), Richard Stallman, 2022/05/08
- Re: gmail+imap+smtp (oauth2), Tim Cross, 2022/05/08
- Re: gmail+imap+smtp (oauth2), Tomas Hlavaty, 2022/05/10
- Re: gmail+imap+smtp (oauth2), Richard Stallman, 2022/05/11
- Re: gmail+imap+smtp (oauth2), Tomas Hlavaty, 2022/05/11
- Re: gmail+imap+smtp (oauth2), Tomas Hlavaty, 2022/05/12
- Re: gmail+imap+smtp (oauth2), Thomas Fitzsimmons, 2022/05/12