I logged into Github today to see if I could give Varnet access and...I don't have admin access. So, could both Greg and I be added as admin to the wikimedia/interconnection-wordpress-theme repo please. (It's possible I didn't act on the invite mentioned in the task above. Apologies.

Related original ask for this repo (that I never got to populating!) T267612

I like this idea if it would make the process less manual than it is currently. I've often found myself spending an entire work day copy/pasting translated text from a Google doc into the Translation interface on-wiki. Given that I'm a monoglot I'm surprised I haven't messed up entire pages (yet).

It's not the canonical repo, just a public mirror. We're working on a better system for sharing and contributing the code behind Diff.

This has been fixed with a recent update to the co-authors plugin. You can now more easily manage multiple authors. See this blog post about the update!

If I understand things correctly, two parts are needed. Commons needs to provide an oEmbed response to requests (such as from WordPress) and WordPress core needs to include oEmbed support for Commons.

An update to our CSS rules broke the calendar interface for a bit. We updated the rules a few weeks ago and things are back to as they should be. :)

Hmm. This seems to be a conflict with the translation plugin. I'll investigate.

Sorry for the delay in responding here. An update to WordPress since this was reported has fixed this issue. The pagination now works as intended.

Thanks @Urbanecm.

• I'll take care of the redirects. No problem.
• Ah, sorry for not being more clear (and for the misspelling of intact!). Please do move the talk page.

I've had my technical questions addressed here and elsewhere. Thanks all for the input.

This is a result of the multilingual software we use on Diff, Polylang. At least in part. It creates a language variant for each taxonomy (categories/tags) when used. This way each category or tag can be written and displayed in the appropriate language (so you don't see a post written in Russian with the English category "Campaigns"). Ideally when editing a post you'd see something like "Campaigns (RU)" or "кампании" in the selection list.

Thanks for trying @Kizule!

see emails sent to assignee on May26 and Jun17

I can confirm that I'm now receiving the digest emails. Thanks y'all for the quick response.

Agreed, this is confusing. The extension we're using for WordPress allows us to have multiple authors, and authors who don't have an account on Diff. It also conflicts with this setting in ways that doesn't give appropriate attribution in the email version of posts. I digress.

My foundation staff account ckoerner@, the other user is kstinerowe@

Note: I am receiving digests for other lists such as wikitech-l and MediaWiki-l.

@CayceP, I was passing by looking at the status of the RSS extension for a project I'm working on. Is this task a duplicate of T147633?

Thank you both @Urbanecm and @MarcoAurelio

Added a note about Diff on the Wikimedia Blog page on meta. That page now references the News section of wikimediafoundation.org.

@Dsharpe You haven't missed anything. We didn't know if it was best to alert you before we made any purchase as we didn't want to buy something only to have Security say no. If it's normal to proceed as you describe I can talk to my supervisor to make that happen.

As per T249039#6309061, medium requires management level acceptance of the risk.

@Reedy et al, are Brad's license updates satisfactory? Anything else needed from our end?

@MarcoAurelio, I hate to be a bother, but is this something you can assist me with?

We had some CSS concatenation issues that were causing the stylesheet for comments to break. That's been fixed in an update from a few months ago. I'm able to verify it's loading as intended. Resolving.

Brad has made the changes regarding licensing (and is also now subscribed to this task). :) 👋

Hi @Reedy! Let me try my best.

Adding a note here that I've spoken to our developer and he is ready for a security review. As mentioned above, the code can be found at the following repo (let me know if you need access).

I'm not sure if there's a way to detect whether the user is using a mouse...That also feels like a bug on Apple's part.

Done! ไทย is now a supported language for string translation. Please let me know if you run into any issues.

@Jcross, understandable. Our timeline is flexible.

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.