[07:54:25] <phedenskog>	 gilles: it was this video I meant about the future of web vitals: https://developer.chrome.com/devsummit/sessions/future-of-core-web-vitals/
[07:55:27] <phedenskog>	 FY
[07:56:11] <phedenskog>	 argh. I'm gonna play with the alerts for first paint and alert manager, so when the alert fire it's because of me!
[19:19:50] <stephanebisson>	 Krinkle: following your comments yesterday about hosting of the Wikipedia Preview images, we started thinking about hosting the component as the primary mean of distribution (instead of npm) and I wrote a task to explore it: T275810. I'm sure you have knowledge and opinions that would be valuable here. Your input would be greatly appreciated.
[19:19:51] <stashbot>	 T275810: Should we host Wikipedia Preview? - https://phabricator.wikimedia.org/T275810
[20:15:01] <Krinkle>	 stephanebisson: Thanks, I'll queue that up. will try to respond by Monday. On the whole, I think I'd lean in favour of self-hosting, but nothing is impossible I suppose. I think it would help us and third parties significantly in terms of performance, security, privacy and compatibility (e.g. which versions do we host, for how many years/decades? though maybe if the script exposes no JS API and is totally self-initiating then it might 
[20:15:01] <Krinkle>	 not be an issue given it degrades fine if it were to go away some day). On hte other hand there is indeed the matter of updating and "getting started", but I think that's a small enough hurdle to not play significantly in major deployments where I'd assume other factors would consume more scrutiny and delay. We have the demo of course for the zero-setup looking around without commitments.
[20:16:46] <Krinkle>	 having an easy to download first-party zip file might also be useful. we don't use or recommend npm for packaging prod code, so we should perhaps not offer this as the (only) method for others either.
[23:34:00] <AaronSchulz>	 Krinkle: just amended https://gerrit.wikimedia.org/r/c/mediawiki/core/+/664415/9 per comments