IANAA (I am not an analyst) so there's little I can contribute to this task, but I wanted to give an example of how this sort of data could be used. I work in Comms for the Foundation and part of my responsibilities is trying to help amplify and share the stories of the movement volunteer contributors. I'm working on a profile of an editor for Diff and wanted to express how their community-building work has impacted editorship in their country. With stats about editorship by geographic area I could say something like, "When Bethany started editing Malagasy Wikipedia in 2014, contributions for their home country of Madagascar comprised less than one percent of total edits made to the website globally. Today it's four percent."

According to the W3C validator / rfc3986 (section 2) the characters for the URL should be found in the US ASCII charset only. Any other letters like accentuated characters eg. é à ç or cyrillic characters in our case won't comply with the w3c validator.

I've updated the blog posts where the invalid images appear. Images are now loading.

Filter will be added in the next version of Jetpack (9.0).

@NSaad Yes! Well, not me directly. :) Comms is working on a process for major foundation announcements that will help with catching major work in the future. In the interm, and if you ever need Comms help (including Diff!), reach out to use at talktocomms@wikimedia.org and we'll talk!

Update: The images not loading is due to a filter added to Jetpack itself that filters the *.wikimedia.org domain for their CDN! This is why it works in development, the domain is go-vip.net, and not production. I'm working with a VIP engineer to add diff. and the other VIP hosted subdomains (policy. techblog.) to be excluded from this filter.

Ah, ok. That's something I can take up with VIP. Thank you for getting back to me.

Hello friends. Is there anything I need to do to help move this along?

A lot has changed since this task was created. The Wikimedia Blog has passed through many hands, was closed, and then reborn recently as Diff.

I didn’t mention it, it was @Aklapper who renamed this task to mention “empty first line” in its title. I deliberately haven’t speculated about what validation error can possibly cause this, because I have absolutely no idea.

This feature has been implemented. A language switcher present on all pages will show content in various languages (where available).

Our hosting provider (WordPress VIP) are looking into the issue. The gist is that Diff is loading intermediate sizes of the images (as WordPress does by default) but we've enabled a solution (an image CDN and scaler service called Photon) that makes the intermediate version of images unnecessary.

A public mirror for Diff is published at: https://github.com/wikimedia/diff-blog

Invite accepted and permissions permitted. :)

Yes, this was handled on the host side of things. Sorry for the noise.

Thank you for reporting this problem. Mmm perhaps this is something related to the theme we are using?

Thanks @Nintendofan885 for the reminder. Resolved!

And published! https://diff.wikimedia.org/2020/08/11/designing-technical-workshops-for-the-indic-community/

@srishakatux How about we write a short summary blog post for Diff, giving folks an overview of the summary and then point folks to the full blog post on the Techblog?

Thanks for the report. I'm working on fixing some of these images. The site is using a different way of handling the resizing of images so some references are broken. It's temporary until we fix the URLs.

Thanks @AdHuikeshoven! Resolving.

I don't think I let the scan run to completion before claiming they were all taken care of. I updated the pages @JFishback_WMF mentioned and re-ran a scan.

Updating project tags to reflect current state.

After a bit of testing to verify, these posts are all redirecting appropriately to their home on Diff. Resolving broadly, but if you find a post where the URL is broken, please file a task and tag it with Diff-blog

Boldly resolving.

blog.wikimedia.org is no more, but its spirit (and archive of posts!) live on with Diff (https://diff.wikimedia.org) Resolving this task as Diff does not load these scripts mentioned. If you do find a related concern with Diff, please file a new task and tag it with Diff-blog

@AdHuikeshoven We've updated the Technology category on Diff to be a little more clear on what is in scope for Diff and the Wikimedia Tech blog. We also include a link to the Tech blog. Does this make things more clear? https://diff.wikimedia.org/category/technology/

I've added OG and Twitter tags to single post views on Diff. Thank you @valerio.bozzolan for reporting. Can you please test to confirm?

I think I have them all now? :)

There was a configuration that was set for the first few days of Diff where images weren't being loaded over http. That's fixed now, so going forward it shouldn't be an issue. I fixed as many issues as I could.

Issue resolved and blog.wikimedia.org is redirecting as expected.

Hey @Reedy legal was curious as to the privacy review. Do I need to create a new task for that? Legal has given their OK for launching Diff, but were wanting to know if you all hand any concerns.

Heh, thanks @wkandek. Sorry for the blank page. I'm working on a fix right now.

Diff has translation capabilities and directions documented.

Github repo will be update (hopefully today) https://github.com/wpcomvip/wikimedia-blog-wikimedia-org

wikimedia-blog is now Diff-blog

@Reedy You have an account (reedy) and I just assigned your account the super admin role. You will have to set up two factor authentication once logged in to get access to all the bits an admin can see/do. :)

Update, as probably obvious, we have pushed the launch date back. Our target date is now July 14th.

Take a look at the /develop branch. It should be in there.

Good questions. I'm going to be bold and suggest we rename it to Diff (blog) and I'll add the relevant tasks in WMF-Communications and we can track them from there.

In T70982#6176378, @Aklapper wrote:

@CKoerner_WMF: That raises some questions (e.g. what happens to its current content). Is there a related technical task about this which has more info?

I updated the task with the current status of blogs hosted by VIP. I've submitted a pull request for the techblog. (https://github.com/wikimedia/wpvip-wikimedia-techblog/pull/2).

This work it at least 4 years old and neither Moushira or I are working on Readers work. Boldly declining.

This work it at least 4 years old and neither Moushira or I are working on Readers work. Boldly declining.