#470 Avatar handling
Closed: Fixed 6 years ago Opened 6 years ago by ryanlerch.

Currently, User avatars are generated and handled by libravatar (this is how it is done on other Fedora services that use avatars, and is tied into the user's FAS name). However, in the config we expose the avatar URL, and allow the user to change it. IMHO, we should remove this item from the user config.

For group avatars, there is code in the models that makes every group avatar a placekitten.com image, but we don't seem to use it anywhere.


I agree that for user hubs we can just use libravatar and drop the config. There's a TODO in the code to implement something "smarter" for group avatars, do you have an idea of what we could do? Just use the default placekitten and allow configuration of an URL in the settings panel?

Metadata Update from @abompard:
- Issue priority set to: High

6 years ago

Metadata Update from @abompard:
- Issue tagged with: needsdiscussion

6 years ago

@abompard on the my-hubs i implemented the basic bones of a simple avatar for group hubs (i abstracted this out a little more in my recent (open) search PR), but i think we just:

  1. remove placekitten from the model, and set by default a hub's avatarurl string to ""
  2. change the populate.py for dev data so a few have "" and a few have a placekitten
  3. further abstract out the myhubs code for generating monogram avatars and use it if a group hub has an avatarurl of ""

Alright, let's do that after the search code is merged, so we can use your improved abstraction.

Metadata Update from @ryanlerch:
- Issue set to the milestone: Production

6 years ago

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

6 years ago

This one is about 90% done after #479 -- all that is left to do is remove the avatar config from the user preferences.

Metadata Update from @ryanlerch:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata