@teledyn@mstdn.ca2025-12-01 19:15:30
Found an obscure hint that perhaps instead of authenticating through #Evolution I should instead authenticate through the #Gnome settings for attached accounts, so I tried that approach, this time it asks for far more permissions (8 in all) but, you guessed it, a classic Sam Beckett "No Answer" and the terse response, "timed out".
So the app doesn't matter. The browser doesn't matter. The account or any legacy cruft doesn't matter.
Does this leave as the only explanation that perhaps Google no longer provides OAuth2 tokens? Surely that would be all over the news if true, but I'm running out of local culprits. Also Emacs inability to authenticate Mastodon suggests its neither google nor Debian per se? Maybe I should spend my time more productively slamming a car door on my fingers?
I have a dread feeling wiping the laptop and carefully reinstalling from scratch will not work.