On Fri, 2016-03-25 at 19:35 +0100, Pierre-Elliott Bécue wrote: > That's in progress, the only goal of this detection is to deactivate > javascript dynamic load of threads. We're thinking about alternative > solutions. I don't understand why you would deactivate JavaScript dynamic load for bots? Typically they don't support JavaScript (except Google) and you should have a fallback for people who turn off JavaScript anyway. I hope mailman3/HyperKitty web interfaces use progressive enhancement: http://en.wikipedia.org/wiki/Progressive_enhancement > I understand your point, and I'll think about it, but my goal is to make > upstream remove obsolete dependencies. django-libravatar seems to be the > only project that bundles support for that, and it's not maintained, whereas > django-gravatar2 is still maintained. I guess you are talking about this project, it hasn't seen any issues filed so probably just works as-is without needing any changes? https://github.com/fnp/django-libravatar > So, for now, I think that I'd rather have a first mailman3 suite in debian, > and then, think about how to make things better. :) I see. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part