It would be great if the gravatar proxy were a service available for all kinds of tools, as there are plenty of potential applications (T191183: Enable avatars in gerrit for example).

I just realized by adding this js snippet we can fix it for now:

$('.gravatar').remove();

There is no need to actually proxy gravatar. We could have our own instance. Gravatar is just a service mapping email md5 to an uploaded image. Is people still uploading their avatars there? Didn't that stop like a decade ago? Even if some people have an image there, it seems saner to use our own "wikimedia avatars". I'm not particularly happy on using the (hashed) email as primary key, but that seems to be what they are working with.

I filed https://gitlab.com/mailman/hyperkitty/-/issues/306 for custom CSS for now.

So the fix is merged upstream, we can probably package it and deploy it?

In T256541#6789243, @Ladsgroup wrote:

So the fix is merged upstream, we can probably package it and deploy it?

Does the fix cleanly applies to the packaged version? if so, it would be enough to just add one further debian patch and rebuild the package.

In T256541#6860002, @Joe wrote:

In T256541#6789243, @Ladsgroup wrote:

So the fix is merged upstream, we can probably package it and deploy it?

Does the fix cleanly applies to the packaged version? if so, it would be enough to just add one further debian patch and rebuild the package.

Just tried it. It doesn't apply cleanly (the patch is rather big and touches lots of places). One way to do it is to actually just package 1.3.4 altogether for buster and use that instead? That's the version that's going to go to bullseye and 1.3.4 has the fix. I don't think it'd be that different to cause issues with mailman itself and they communicate through REST APIs so I hope it'd be stable.

Related, mentioning just for cross-linking: T263161: Set up a Gravatar proxy in Wikimedia production