I gave KDE access to my Google account, I was asked for a confirmation code by phone 3 times and then I had to confirm the confirmation codes by phone again, everything went well - access was granted to KDE and they can do whatever they want with my account.
I would like to know: when will KDE, in return for granting access to my account, grant me access to Google Drive?
p.s. the binding did not work with application passwords
Sorry to inform you google has restricted KIO support for no apparent reason and mandates the KDE community to do go through stupid bureaucratic steps to hope to fix this:
I studied the provided access to see WHAT EXACTLY Google allows to use: there is Youtube and Calendar, but no Drive, despite the fact that when providing access it was indicated - Mark all.
Most likely, KDE is misleading users by indicating that KDE Online Accounts provides access to Drive, such access is NOT, but there is access to use and change my Google account data 
Documentation has not been updated, thatβs all, code has been to stop asking for drive access, since it wonβt be used.
Again thatβs google doing really.
got it - thank you
Itβs very strange that Google doesnβt provide access by application passwords, thatβs exactly what I thought, that it doesnβt work because of this, but entering the application password didnβt help
The issue has been resolved: the network account has been removed from the settings
So is there any alternative? Is there no way to mount a Google Drive as a drive in linux?
I read somewhere else that developers just need to update their security codes. It seems nothing has been updated in some time now.
The current status of KDE Frameworks being able to access to Google Drive is, as far as I know, unchanged from Nateβs comments on this bug report from last year: 480779 β Can not add Google to Online Accounts anymore using a recent version of signon-ui
Google blocked us from using this back in June because we werenβt able
justify our API usage to their satisfaction.
Most KDE developers minimize their usage of Google services these days, so the overlap between βpeople who care about Google Drive integration workingβ and βpeople who have the interest and time to engage with Google to prove the security of KDEβs Google Drive client implementationβ is becoming smaller over time. Thatβs the backstory to why this broke, why itβs not fixed yet, and why even my exceptionally crude change took so long to get done.
If anyone wants to take initiative to communicate with Google directly on KDEβs behalf to prove the security of our Google Drive client, and then also do it again every year when they make us re-certify, and then also do it again randomly when they tighten the requirements again, please let me know and Iβll be happy to direct you to the right place.
That is something I could do. Could you spend a few minutes in teaching what to do, in order to do it correctly?
