On Friday, 06.05.2022 at 22:23 +0800, lilydjwg wrote: > On Fri, May 06, 2022 at 03:10:37PM +0100, Dave Ewart wrote: > > [...] > > > > Hmm, so "testing mode" is where I did the initial setup to hardcode the > > tokens into my (encrypted) config? > > > > So it sounds like maybe I don't need to do anything, but is there a > > better way that doesn't use 'testing'? [Maybe it's not needed, I've been > > using the single 'testing' setup unmodified since late 2020!] > > AFAICT testing mode isn't affected and can continue to work as before. > That 'testing' means that you can only add limited testers to use your > app (the thing that has a client_id etc). For personal use the only > annoying part I find is that the access code expires every 7 days.
What are the implications of the access code expiring? I don't see any symptoms which might be associated with that and the Mutt client is running in 'screen' 24/7/365. Testing with a single 'user' of my 'app' is fine: it's just me talking to my Gmail :-) Cheers, Dave. -- Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart All email from me is digitally signed, http://www.sungate.co.uk/ GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197
