That sounds good. Thank you!

Tangential question: Is there an alternative way to get to the list of the currently active translators in a language?

Unassigned per T64559#6752447

Hi @GShriya this is a very complicated task. If you are looking for places to start out, I suggest looking at good first task and https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker

Oh, I see. I thought it was still the full-page-width classic "OBOD", as documented at https://meta.wikimedia.org/wiki/New_messages_notification ? My quick test didn't work, so I can't confirm either way.

In T14681#6745279, @Jdlrobson wrote:

I think this should be declined given Echo ?

Those were helpful, thanks Mahir256!

In T270792#6710981, @Legoktm wrote:

https://species.wikimedia.org/ is already allowed

In T258492#6492352, @Elitre wrote:

TYSM! I will figure out where to put this ASAP ^_^

See also related old discussion in T56604: Large number of CSS rules for external links (especially Krinkle's technical comments there, which might still be useful here?).
My 2cents: As I wrote there in 2013, I think some of the icons were very useful such as those for media files (to avoid nasty surprises like sudden loud sounds when I'm sitting in a library) and mailto: links (which often open a program or tab that I didn't want to have open).
I strongly agree that we used to have far too many, and some skins still do (e.g. Modern still has the https padlock), but I'd welcome the return of a few in Vector/everywhere.
Hope that helps, and that this is the correct location to comment. :-)

One more new example of a duplication.
first send (22:10) and second send (22:11).
I've checked ~50 other random entries from the distribution list I used, and that was the only duplication I could see.

Perfect, thank you!

@Urbanecm /anyone: do you have a suggestion on how to phrase this in Tech News? I'm not sure how to summarize it, based on what is above.
I searched Tech News archives, and it seems the last times we mentioned TLS or old browsers were in 2020-01 and in 2018-06.
You can also add it directly (this week's issue) yourself! :)

@cscott From interwiki links, I see a few are localized. Should that be done onwiki or at translatewiki?
Ah, yes, after searching down various rabbit-holes I found it at https://translatewiki.net/wiki/Special:Translations?message=Nonnumeric-formatnum&namespace=8
Aha, and from that, I found the page where these are meant to be documented! https://www.mediawiki.org/wiki/Help:Tracking_categories - It is not currently listed there so please add it! :-)
For Tech News, I've spent over an hour wrestling with how much to say, and it's still very complex yet missing details, but I need to freeze this week's edition for translation, so I will put it in next week's edition (for delivery 2 November) - please amend or improve the item at https://meta.wikimedia.org/wiki/Tech/News/2020/45 or comment on the talkpage there. Thanks!

Grah! It's been a long week. Thanks/sorry!

Just noting: @Tacsipacsi has helpfully rewritten the version in the draft to be more accurate (and especially thankfully, did so before I sent the 1st email to translators-l@!). That new version looks good to me, so I will leave it like that.
For future reference, it is always appreciated if people write out a draft entry for Tech News at the same time as they tag a task with User-notice. That saves us editors a major headache of trying to deduce what a task is all about. Thanks in advance! ;-)

For the purposes of a potential item in Tech News, please could someone clarify whether this is a bug-fix that all the wikis need to learn about? I've tried to understand it by skimming the thread, but I am unable.
If you believe it does need to be communicated broadly, then please help by drafting 1-2 sentences explaining how, and how much, did it impact users. E.g. "There was a problem with X that resulted in Y. This has now been fixed." Note: we try to only send out information about the most high-impact bugs, that affected many wiki communities, so as to not deluge everyone with too much information. (cf. contribution docs)
If you believe it does not need to be communicated broadly, then just remove the #user-notice tag!
Much thanks.

For the user-notice in Tech News, does this accurately describe the item? If not, a clearer/better draft would be appreciated. (and for future reference, writing them for us when you add the tag is always appreciated! ;D )

There was a problem with the links to "diffs" from mobile watchlists and recentchanges. This has now been fixed. [1]

For the user-notice entry in Tech News, is this accurate? If not, a rewritten or simpler/clearer draft would be appreciated :)

There was a problem with the [[Special:Tag|Change Tags]]. The software would apply the "{{int:Tag-mw-reverted}}" tag to any null edits such as page-protection changes that came after a reverted edit. This has now been fixed for new edits. [1]

I think "improve documentation" covers it!
I.e. for this task, if you/anyone notice any redundant replication/slow-drift-forking of content (that should be kept consistent), then stick it in a template, like was done with https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication (the header and table from that are transcluded in many places).
[p.s. Obligatory https://www.mediawiki.org/wiki/User:Quiddity/Zanzu ]

Hi @Jdlrobson If I understand correctly, the wording in the user-notice should be something like:

Some gadgets and user-scripts use the HTML div #jump-to-nav. This div will be removed soon. Maintainers should replace these uses with either #siteSub or #mw-content-text. A list of affected scripts is at the top of phab:T265373.

If that is inaccurate/imperfect, then Please provide a correct version.
I will add it to TechNews tomorrow (Friday) morning (PST) before this issue is frozen for translation, for delivery on Monday.

In T213778#6509613, @Jdrewniak wrote:

[...] Many different types of links have icons associated with them, (like external, or pdfs, or maps) I think that approach could work for external wikimedia links too.

In T213778#6500539, @Wugapodes wrote:

I like this general idea, but not all interwiki links go to WMF wikis, so the specific icon would be misleading. [[Special:Interwiki]] shows that most of our supported interwiki prefixes point to non-WMF wikis (and many non-wikis) so it may be better to just treat interwiki and external links as the same for styling purposes, but allow power users to define custom behavior.

Question: is there some way to use the fallback language's parent language? I.e. we frequently get translations in pt-br, and not in pt. When we deliver these massmessages, the Ptwikis all get the English version. We want to fix this situation.

@Aklapper You can either use https://www.mediawiki.org/wiki/Special:Import (the drop-down menu includes enwiki), or use an edit-summary like "copying content from [[w:en:Module:....]], see which for attribution"

See also T239875: VE leaves around inline data-parsoid on edited content.
I was getting this Error 500 on officewiki last week, and assumed it was related to that task still.
I believe a temporary workaround, is to create an empty page first (with dummy edit), and then edit it again with VE. (Or at least in my brief testing, I could paste the richtext content into an existing sandbox page on officewiki, but I could not create it as the first revision of a page). HTH.

I've rewritten the task to hopefully make it clearer. @Johan please revert or correct if I've misunderstood or imperfectly-described anything.

Looks great! Thank you :)

Created Okapi

Ah, thank you @Tacsipacsi for that tip.
@AlexisJazz I believe the underlying-problem that I was trying to fix is related to a different bug, T239921: Translate extension failing to load translation aids (per the same error message, "Title does not correspond to a translatable message"), not this one?

Sorry I didn't see this message until after I had frozen the issue for translation. (I missed checking a column in the workboard). Instead of altering the now-frozen-for-translations issue of TechNews itself, I have added a note into this task's description. Hope that works!

I think the Con of "Can't in future filter things out of watchlist/recent changes for alterations to languages the user doesn't care about" might potentially be a major concern for options A and B. This is an important feature to have for content-maintainers, in order to control the signal-to-noise ratio in our change-patrol systems, if we're expecting fairly high-velocity RC feeds. -- Is there any upcoming work around T246749: Ability to filter by label language in Wikidata RC in other projects that might help resolve this?

@matej_suchanek Thank you for writing the explanation! Is there a link that we could add to this, to give more details?

If I understand correctly, this is not yet ready for announcement. For once it is ready, please could you provide an explanatory entry for TechNews. Just 1-2 sentences explaining what the change is. Thanks!

Is this intended to be summarized in TechNews this week? If so, could someone please write a short (1-2 sentence) clear summary for inclusion? Thanks.

Hi. Is this now ready to be included in TechNews, or should it wait for next/future week's? (the User-notice tag was added in 2018!)
Whenever it goes in, please suggest wording for the inclusion, e.g. "Logged-in users will now receive a Notification if their account has been blocked."

In T231522#6335014, @Ammarpad wrote:

Yes, I think with the newer approach this need not be communicated at all as the maintainers are willing to support the current usage, so there'd be no user facing change.

Yup. The general process is explained at
https://meta.wikimedia.org/wiki/Newsletters/Translation#Regular_process
as linked from
https://www.mediawiki.org/wiki/Help:Extension:MassMessage#Sending_a_translated_message