Talk:Blog Content Curation and Original Writing Guidelines

i0.wp.com

Stacco, could you explain why you ask people to use i0.wp.com ?

Thanks Simon Grant (talk) 05:39, 25 November 2016 (UTC)

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.

Thanks Stacco Troncoso (talk) 13:38, 28 November 2016 (UTC)

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!

One question remains in my mind: do we "pay" for this service by having image information tracked and monetised by wp.com? Thanks Simon Grant (talk) 13:32, 28 November 2016 (UTC)