@Jdlrobson Thank you. Simplified the sentence structure and added it to https://meta.wikimedia.org/wiki/Tech/News/2019/47 which will be delivered to the wikis on Monday November 18.

I honestly don't know if there's a good candidate. Sakti? Dan Foy? (Probably not Dan, they were disconnected a bit through the project.)

When would this happen?

When it comes to re-enabling the feature ... we should be aware there's a fair number of reverts of good-faith edits because people don't grasp what the wikis are about, but our workflows should mainly avoid running into them as we're streamlining what people can do here. If we have already paused the functionality in a first step, then unpaused, and then it gets disabled, I've got no good idea for where to go from there.

Regarding the helpful links: No, as far as I can tell, we've got a new use case here – the wikis have been solving this in different ways, and maybe we could manually compile a list but that would be basically going around everywhere asking people what their best page would be, and then getting wildly varying results. We're tying to get people to set something up, but for the time being I'd assume that if we want something we'd have to write it ourselves.

OK, adding it to the issue going on Monday, and we'll figure out if it should be in "later this week" or "future news" before the issue gets delivered.

(My comment edited to reflect this.)

Roughly when would we expect this to be in production?

As far as I can tell, this is resolved. Checked in with them a while ago and there was no request for my help.

If we've got es, zh, fa we might want to look at en, as an outlier, and maybe ... uk and/or vi? Just looking at it from the outside, they're about a size that would be interesting, small number of CUs.

I've no good solution for this at the top of my head, but I'll ask around.

(There's another problem I had to work around, and accidentally included some who had already got the newsletter when I sent it out the second time. Mea culpa.)

Yes, this is human error. See explanation here:
https://meta.wikimedia.org/wiki/Talk:Tech/News#Week_42

Another week when Tech News wouldn't deliver if the MassMessage target list was too big.

In that case, we don't need to take the less efficient way of writing in Tech News, better to contact the wiki directly.

OK, added.

When more exactly will it be deployed to all wikis? We had a mention of it in #29 but should update again once all wikis have it, of course.

This only affects English Wikipedia, right?

This has now been added to Tech News.

Thanks. Rephrased slightly to fit with the style of the newsletter; it has now been included.

Something like this for Tech News? (Plus links and clearer handling of URLs.)

How would you phrase this for inclusion in Tech News?

Thanks for the quick fix. Much appreciated.

Successfully delivered to my test list of seven pages.

Does that mean that the jobs didn't include the undelivered messages?

Just to contextualise – among other things, this means that the weekly technical newsletter on which we rely to inform the communities about upcoming problems, changes, new features, feedback we need to get on tools being developed and so on can't be delivered. Basically, we're very limited in our ability to talk to the communities.

Yeah I tried to send a message to to my test list to deliver Tech News but one message out of six made it so I don't think there's much point in trying right now.

OK, made it shorter for ease of translation but tried to keep your explanation of why.

If this is to go out next week and you want something about a script included in Tech News, that needs to be available at latest 14:00 UTC tomorrow Friday.

I'd still prefer "can" instead of "will find opportunities to", but if you think it's better as it is, then I've got nothing else that I react to when reading the current copy. (:

"Consecutive" might also be a tad difficult for someone who wants to use the app for other languages than English.

So I should have thought of this earlier, but in general, I think it would benefit us if we made the language simpler. Even if I want to read and edit in a language that isn't English, in most cases, I'd still have to use the English interface. A few comments on the language as is shown in the images in general, not just here.

Looks OK?

@Jdlrobson @Volker_E When is this going to be in production, if you know? Do you still plan on a script before you go ahead with anything?

I suspect this is the reason why MassMessage isn't delivering Tech News to most subscribers. We're getting a good number of complaints, as the editors don't know what's happening – we can't warn them of changes that will happen, they're missing calls for action to tell us about problems some changes will cause, they're unaware of new tools and so on.

@doctaxon I'm not sure exactly what it is you're asking? The problems with multiple deliveries stem from the problem discussed in this task, for which a fix is being merged now. If you've got general questions about Tech News and how it's being delivered, I suggest you ask them at m:Talk:Tech/News and I'll be happy to answer.

Presentation written and given.

In that case, I suggest getting said deduplication flag. It's bad that we're spamming people.

Looks good to me.

Sorry, my misunderstanding. I'd still not link to English Wikipedia, unless we're specifically showing it in an instance where the user is trying to edit English Wikipedia while blocked on English Wikipedia – i.e. not in our suggested edits, where they actually edit Wikidata.

I would avoid linking to the https://en.wikipedia.org/wiki/Help:I_have_been_blocked page – it's specific for English Wikipedia in some ways, with links to appeal to the decision that will be confusing since they're not blocked in that sense, they just can't use this specific workflow in the app.

@bd808 added it to Wikitech too.

Also, Ukrainian Wikipedia hasn't got Tech News since September 4. This is limiting our ability to communicate any technical changes to editors: what's happening, what do they need to prepare for, what can they give feedback on – leading to tools having bigger potential to remain unused, preparations not being taken, and risk of conflict when they were not invited to discuss things that might change their workflows. Is that likely to be caused by T232392?

Have we seen any arguments against a new deduplication flag so far?

Hadn't planned for meetings that late on the Wednesday so I think I might be passing through some tunnels south of Stockholm around that time, but I'll join you if the connection allows me to.

Now, yes.

I see no reason why this would be an area of conflict. If we can make sure this doesn't happen in the future in a way that wouldn't have other adverse effects, I'm sure most folks would agree that's great. If we can't address them without adverse effects – is this a common problem? No one wants the content obscured. The template was promptly removed by one editor for getting in the way, and another editor pointed out on the talk page that it's not supposed to be used in articles.

Something like this for Tech News?