12 ms·
What a terrible communication from Google if even tech savvy people can't understand what's exactly changing for them.
by siva7 2y ago
What a terrible communication from Google if even tech savvy people can't understand what's exactly changing for them.
- boneitis 2y agoThere's plenty enough stuff to blame Google for. I'm happy enough this time to blame my own lack of willingness to invest any more time, now that this feels certain that I'm unaffected :) For anyone who needs to dig deeper, this so far seemed the most pointedly focused first-party documentation on the topic (though again, I'm not actively investigating it): https://support.google.com/a/answer/14114704 https://support.google.com/a/answer/14114704
- makeitdouble 2y agoWhile Google is making the change and 100% responsible for the mess, the work to understand the impact and adapt to it lays on the application devs and users. I don't think there's any reliable way Google can properly guide users to deal with apps they don't (and shouldn't) control. You and me would be properly horrified if Google could dictate how Outlook auth works and what exact steps will help the user transition, whatever the Outlook team decides to do on their own. The most they can do will be to help the app developpers to prepare for the change, and vaguely gesturing at users about potentially impacted settings.
- cpach 2y agoIndeed. They should explicitly state either “App Passwords will no longer be accepted after <deadline>” or “App Passwords will still be accepted even after <deadline>” depending on which is true.