Re: getmail-gmail-xoauth-tokens patch 1
Scott Robbins <[email protected]> Thu, 5 May 2022 11:06:29 -0400
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, May 04, 2022 at 09:19:37PM -0600, Charles Cazabon wrote: > Tyrel McQueen <[email protected]> wrote: > > > > This is the first of two potential patches for the oauth2 support script of > > getmail. If one creates an OAuth2 client_id that is of type webapp, then > > two additional parameters need to be passed in order to receive not just an > > access_token, but also a refresh_token. The patch below accomplishes that. > > Thank you for the patch! > > > Yes, I don't see any other alternatives to that method. It's particularly > stupid. Yes, in my original reply I wrote due to google's attempt to make everyone use their products---err uh, make email safer, then discarded it trying to be nice. But since you said it, I have to say, Definitely! I'm trying to move more of my stuff from using google. > > Google/Gmail, the 900lb gorilla of email today, is constantly pulling bullshit > like this, deliberately trying to make using any other email > client/system/provider have more friction than "screw it, I'll just use > Gmail". -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6