The Editing team will discuss this topic on December 18.

Isn't the Impact module updated twice a day?

@Sgs None of the Growth features are enabled at any Wikisource.

Final copy for Tech News:

"When Citoid generates a reference based on an archive.org URL, we currently have no way of populating the archive-url and archive-date parameters in the citation template. The archive.org URL is considered the "original" URL, not as an archive link. The Editing Team is working on fixing this. We are asking communities to add two parameters preemptively, <code>archiveUrl</code> and <code>archiveDate</code>, within the TemplateData for each citation template using Citoid (example of change in a template, list of all concerned templates). "

I would add a comparison point with Notifications given by the icons:

• Talk pages notifications
• Talk pages subscription notifications.

You both know better than I do if move right require the create right. :)

I didn't notice this task until now.

This project will resume in January 2025.

Thank you for reporting it @Wladek92, and sorry for the disturbance.

In T381295#10372534, @DLynch wrote:

Also disable it for NS_PROJECT_TALK there?

It seems to be unique to Catalan Wikipedia (for phase 2a): T159047: Enabling Flow in cawiki 'Viquiprojecte Discussió' namespace.

I checked the logs at T378827: Run Flow migration script at *Phase 1* wikis. Skipped pages were all checked and I manually moved https://pt.wikipedia.org/wiki/Ajuda:Contato/Fale_com_a_Wikip%C3%A9dia.

I checked the logs and everything was moved successfully.

The problem with fi:Keskustelu käyttäjästä:Trizek (WMF) was solved thanks to @Zache.

All wikis have been informed, per T380316: Inform Phase 1 wikis of Flow removal plan and timing with a deadline regarding manual moves. I'm assisting the ones that request my help.

I saw the issue before reading your message @Msz2001. As you may have noticed, I manually posted the update at Pomoc:Pytania_nowicjuszy.

Less a priority as the process now targets German and English (T367343), where VE is not the default experience.

I filled T380272: Extract data to assess the percentage of edits reverted because of copyvio risk as I'm blocked on the data extraction. (cc @ppelberg)

I believe this is the start of scaling. Good thinking about scaling will help us in the future.

• We should decide the maximum number of checks shown to the user within the same session
• We should have a way to prioritize checks by type, eachgetting a unique order number.
  • This goes along with the priority of the check, given by the level of importance the community gives to each check
• Based on both, we calculate which checks should be shown first.
  • This implies having a way to show the total [shown + unshown] checks somewhere, and a possibility for the user to explore them.
  • Should we show new checks when the first shown are fixed? I would say yes if we have a good way to inform the user that more will come.

In T380062#10328165, @Pppery wrote:

Note that this seems to be the Beta feature being disabled, not the maintenance script that moves to subpages which uses different code.

In T379984#10324872, @ppelberg wrote:

Assuming it would be relatively straightforward to revise this naming scheme if/when Benoît identifies a reason for us to do so, let's moving forward with implementing this as you propose, David.

Let's go.

Yes, this is the kind of manual cleanup we anticipated to make. However, now that the read-only is applied, non-one can contact the user. We need more time before the read-only to finish the cleanup.

Dates regarding Phases 1 and 2 will be discussed with the Editing team on November 13.

In T370722#10295685, @kostajh wrote:

@ppelberg the task title mentions LiquidThreads (related T350164: [Spike] Investigate Undeploying LiquidThreads), but the work here seems specific to Flow. Is there a plan/timeline for LiquidThreads as well?

Any option is fine for French as long as:

1. the result remains «[no brake space][content][no brake space]» in final rendering,
2. the change is not noticeable (we fill in the configuration before releasing).

I'll let @tstarling reply on the pretty fallback issue. This wasn't documented for no reason.

In T223772#10248025, @IKhitron wrote:

In T223772#10247886, @Trizek-WMF wrote:

if it is not supported, the "date" format is used.

This is wrong. Many languages that has no "pretty" defined use "j F" that has no sence.

Do you mean that date is not used when pretty is not defined? Or something else?

I'm arriving from this conversation, where pretty is discussed.

In T371738#10236325, @Bugreporter wrote:

My advice it to let the user decide, as the former wikitext talk page can be very outdated. For some users, Flow was their main talk page system for 9 years.

Currently if Flow is used as Beta Feature and user turn off it (no matter when it is turned on), the old archived talk page is moved back. An mass conversion script should keep such behavior for consistency.