Talk:Blog Content Curation and Original Writing Guidelines
Stacco, could you explain why you ask people to use i0.wp.com ?
Hi Simon. This was suggested by our SysAdmin, Javier Arturo Rodríguez for images that didn't have https. I would prefer the process to be automatized somehow to make the process easier for blog contributors and encourage more participation. Maybe Javier can suggest something.
In fact the intention is to avoid mixing "secure" (HTTPS) and "insecure" (HTTP) content - since the wiki is on HTTPS, browsers should (and most do) ignore inline HTTP content, thus the need to include external resources through an HTTPS cache/gateway. I would rather have all relevant images included through HTTPS if the origin sites support it, or directly copied to the wiki - but this last option might be unsustainable, size-wise, in the long term.
A side effect of using a cache is to avoid hammering other people's servers from an image inclusion in a popular article, keeping bandwidth leeching to a minimum.
A compromise we'll try to pursue is to take all http:// image SRCs and translate them automatically into https://i0.wp.com/ URLs, but that's not very high in our priority list ATM. Codehead (talk) 13:01, 28 November 2016 (UTC)
Many thanks for this really helpful explanation, particularly helpful to a mere semi-techie like myself!
Image usage is definitely being tracked because that's necessary for any competent caching algorithm. The image metadata could be used to gauge site or resource popularity. I might be wrong but I don't think it can be monetized in any way, or more companies would be doing it for free. Codehead (talk) 13:42, 28 November 2016 (UTC)