https://bugs.kde.org/show_bug.cgi?id=480779
--- Comment #51 from Marc <darkstar...@gmail.com> --- (In reply to Nate Graham from comment #50) > JFYI, the solution to use the GNOME configuration file is no solution at > all; it's essentially impersonating GNOME and piggypacking on the work they > *did* do to retain permission to access Google Drive that KDE wasn't able to > do yet. If Google finds out about this, it's likely they'll revoke GNOME's > authorization too to prevent others from using it for software that wasn't > approved, permanently ban KDE from accessing Google Drive again, or both. I think the line of reasoning presented isn't "KDE should just steal the gnome config" but more along the lines of GNOME seems to have engaged with google and properly resolved this including the google drive concerns and could we find out who is in charge of managing these APIs/etc and assign this to them so that they can engage with google to properly fix this instead of removing functionality? It seems like at that point, we already know the current code itself is sound so any changes made to remove functionality here to make it work now would end up reverted, so would end up just being wasted effort, even if that effort is minimal. -- You are receiving this mail because: You are watching all bug changes.
