3 ms·

Gnome has an component, Gnome Online Accounts. It's purpose is to provide and manage account information for applications that need it, so the user doesn't hav

Gnome has an component, Gnome Online Accounts. It's purpose is to provide and manage account information for applications that need it, so the user doesn't have to configure their email, calendar, whatever, in each application separately. With each application storing passwords in a who knows where, or each implementing their Gmail OAuth. So it is quite logical, that application that uses accounts will also need gnome-online-accounts. 'Do one thing and do it well` -- how is that anti Unix philosophy?

jcranmer 3y ago
> With each application storing passwords in a who knows where GNOME has a keyring system service for storing passwords, so it's not necessary to get the entire desktop shell to access the keyring.
- vetinari 3y ago
  Keyring is another component, specifically for passwords. GOA is for storing account information: e.g. you configure your Gmail/nextcloud/whatever account once, and then all apps that need it can access it. So your Geary, Contacts and Calendar (separate applications) do not need each to implement account management and account specific auth flows -- not just passwords, OAuth is all the rage nowadays. And I, as the user, do not have to keep tokens in each app current. It is also not 'entire gnome shell`. Just the required components.
gryn 3y ago
sure but to setup gnome online accounts the official documented way you need gome-control-center, other ways to do seems to not have official documentation and have failed me. here the required dependency list for control center on arch: accountsservice bolt colord-gtk4 cups-pk-helper gcr gnome-bluetooth-3.0 gnome-color-manager gnome-desktop-4 gnome-online-accounts gnome-settings-daemon gnome-shell gsettings-desktop-schemas gsound gtk4 libadwaita libgnomekbd libgtop libgudev libibus libmalcontent libmm-glib libnma-gtk4 libpwquality smbclient sound-theme-freedesktop udisks2 upower while it may follow the letter of the philosophy is certainly doesn't feel like it's following the intent of it. the components form a sort of cyclic graph, where technically you can install any component but soon you'll find that you need all the others with no viable alternative component that will work reasonably well. using these component outside of the DE feel like being a second class citizen that will be kicked out at any update, and then you'll have to scavenge for information from unofficial sources and the source code for what has changed that broke your setup.

jcranmer 3y ago

> With each application storing passwords in a who knows where GNOME has a keyring system service for storing passwords, so it's not necessary to get the entire desktop shell to access the keyring.

vetinari 3y ago
Keyring is another component, specifically for passwords. GOA is for storing account information: e.g. you configure your Gmail/nextcloud/whatever account once, and then all apps that need it can access it. So your Geary, Contacts and Calendar (separate applications) do not need each to implement account management and account specific auth flows -- not just passwords, OAuth is all the rage nowadays. And I, as the user, do not have to keep tokens in each app current. It is also not 'entire gnome shell`. Just the required components.

gryn 3y ago

sure but to setup gnome online accounts the official documented way you need gome-control-center, other ways to do seems to not have official documentation and have failed me. here the required dependency list for control center on arch: accountsservice bolt colord-gtk4 cups-pk-helper gcr gnome-bluetooth-3.0 gnome-color-manager gnome-desktop-4 gnome-online-accounts gnome-settings-daemon gnome-shell gsettings-desktop-schemas gsound gtk4 libadwaita libgnomekbd libgtop libgudev libibus libmalcontent libmm-glib libnma-gtk4 libpwquality smbclient sound-theme-freedesktop udisks2 upower while it may follow the letter of the philosophy is certainly doesn't feel like it's following the intent of it. the components form a sort of cyclic graph, where technically you can install any component but soon you'll find that you need all the others with no viable alternative component that will work reasonably well. using these component outside of the DE feel like being a second class citizen that will be kicked out at any update, and then you'll have to scavenge for information from unofficial sources and the source code for what has changed that broke your setup.