FYI, You can also change the avatar initials, by changing the name associated with the account.
@Shuckle, in this case, Discourseâs implementation - like Bitwardenâs - uses such standard components in such a predictable manner that the design is trivial. Storing personal user data in an inefficient (bitmap) form, at scale, isnât necessarily. You have compression to contend with.
Though, in retrospect, they have already created a file upload mechanism for vault entries, and presumably these are encrypted.
Indeed. It seems mighty strange that they spent time creating the dialog without doing it properly, because even if there is more to do, they were working on it and used to poll and cache Gravatar.
@grb, Iâd have preferred that they retained that. I and many others are used to using Libravatar and Gravatar.
I am not privy to Bitwardenâs decision-making process, beyond any comments by Bitwarden staff that can be found on public discussion forums.
It seems that the avatar framework used to implement the color-picker is different from the avatar framework that was previously used to support Gravatars. Perhaps there is no suitable avatar framework available in NodeJS that can simultaneously support both.
Also, one benefit of the new avatar framework is that it is synced â once I set up an avatar color (and initials) in the Web Vault app, it syncs automatically to all other apps and browser extensions. With the old avatar framework, Gravatars were disabled by default and had to be enabled in the app or extension preferences â however, this preference was not synced across apps.
@grb, irrespective, I would have preferred Gravatar, since thatâs a more broad problem that theyâve yet to remediate. Such stopgap measures of solely synchronising certain preferences at seeming random is inadequate:
Enabling that Gravatar synchronisation preference alongside all the rest I must configure each time I authenticate for the first time in a browser profile wouldnât be of any significant difficulty.