In T423737#12142779, @HCoplin-WMF wrote:

I think the one issue I have with https://wikimediafoundation.org/news/2026/05/19/want-to-read-more-download-the-wikipedia-app/ is that the content is really heavily promoting the 25 year anniversary & reading challenge. That is already fairly out of date since the reading challenge is already done. Another option would be to have a more generic page on the foundation site that highlights the mobile app; I just don't think we should hard code a link to an article that is already fairly irrelevant. In that page, the later content is more relevant, but also doesn't seem to support section based linking. We could add that, but it still seems a little strange to link to a news article.

@JScherer-WMF - can you please take a look and confirm that this prototype sandbox is no longer in use? If so please feel free to close task as invalid

oops closing old item completed offline - Nico met with Bethany and made recommendations re task 2 and 3,

In T419775#12109720, @HCoplin-WMF wrote:

Hey -- just checking in again. Any idea of when this might be available? For more context, we have another hypothesis this quarter for the Attribution API, which includes improving our calls to action. One of the main calls to action we would like to include is basically "download the app" so getting this up and running would be ideal. We can figure out a temporary workaround that improves on the current experience, but knowing if/when you might pull this in would be helpful to know.

Until the T419775 is completed, an alternative URL to go to may be this recently added info page about the apps on the wikimediafoundation site: https://wikimediafoundation.org/news/2026/05/19/want-to-read-more-download-the-wikipedia-app/
It has the benefit of having more prominent download links and providing information about the app (vs the portal page) and more mass-audience friendly than the mediawiki pages.
(cc @Sarai-WMF)

Apologies this was completed a while back.

Thanks @Miriam et al for your review and detailed notes! It's helpful to know that wprov is a viable solution for measuring impact. Confirming the intention is that being able to measure impact would always be a pre-requisite for our IR2 interventions.

In T422587#11803881, @Krinkle wrote:

I'm writing an essay on the topic, but in a nut shell: The unintended use of no-referrer and other mechanisms like it has fueled industry dominance of Google and others, making the broader ecosystem of websites like ours incorrectly believe that they are dependent on Google for 90% of their traffic. What has happened is that tonnes and tonnes of websites have blindly followed security theatre around Referrer-Policy, without understanding what this does or what choices you have. The consequence is that all of these websites have erased their own footprints, thus making it seem that all traffic comes from Google. It is a true tragedy of the commons, because whenever one site does this, they still see others, but others no longer see them, and over time, nobody sees anybody, except we all still see the handful of sites in our analytics don't follow do this: big search engines and social media sites. There are other cases I'm researching where this is even worse.

In T422587#11802049, @CKoerner_WMF wrote:

Hey @Krinkle do you think we need to have the Security folks take a look at this change?

I think matching what our most sensitive sites use in production (en.wikipedia.org, uk.wikipedia.org, zh.wikipedia.org), what experts like Scott Helme recommend, and what privacy advocates like WebKit and Mozilla use as the strict default in their browser, should be good enough for our blogs.

Thanks for raising this Sarai! This fits into the long term vision to help any Reuser including AI agents to follow best attribution practices. Something to a "robots.txt" but for attribution instead. Some parallels also with Bsky's user intents proposal https://github.com/bluesky-social/atproto/discussions/3617

hi @HCoplin-WMF - can you please advise on the API beta URL and expected date once ready? Thank you!

Adding current designers on ModTools/Watchlist

+ @DTorsani-WMF for inclusion in the Codex icon audit/review.

Thank you! I retested the issues and TLDR all looks good ...details below

Latest design review (using wikivoyage):

Just tested on wikivoyage and visual notice on footer LGTM:

Review description	Screenshot
Desktop footer V2022
Mobile footer (Minerva)
Old popup - no longer appearing

In T363484#11015070, @cscott wrote:

Current patch demo is at https://649538b6c5.catalyst.wmcloud.org/wiki/New%20York%20City and is ready for review. I had to make a few tweaks to the design to accomodate the selected backend (posting to a talk page). In particular, I needed to provide a topic for the post and also to inform the user of the page where the message would be/was posted.

In T363484#11015070, @cscott wrote:

Current patch demo is at https://649538b6c5.catalyst.wmcloud.org/wiki/New%20York%20City and is ready for review. I had to make a few tweaks to the design to accomodate the selected backend (posting to a talk page). In particular, I needed to provide a topic for the post and also to inform the user of the page where the message would be/was posted.

Adding @Sarai-WMF in case there's design review needed while i'm ooo until Jul 14 :)

In T363484#10955544, @cscott wrote:

In his review, @Arlolra pointed out that the footer text is not used in the MinervaNeue skin. (I tested every other skin available on patchdemo and they looked fine).

MinervaNeue looks like:

Any thoughts on where the 'rendered with Parsoid' text should go for this skin? I'm thinking in the footer, as another item in the "Privacy policy Mobile view Developers Statistics Cookie statement" list.

In T363484#10937870, @PatchDemoBot wrote:

Test wiki created on Patch demo by RHo (WMF) using patch(es) linked to this task:
https://patchdemo.wmcloud.org/wikis/5ab5d73ccc/wiki/New York (magazine)

In T363484#10932402, @cscott wrote:

Sorry, you'll need the parser migration extension installed, and to have parsoid read views enabled for your account:
https://www.mediawiki.org/wiki/Help:Extension%3AParserMigration
That is installed on beta and testwiki, I believe, so it should just be a matter of enabling parsoid read views in your user preferences.

For patch demo, there's https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ParserMigration/+/1100121 which I think can help, but I haven't tried this myself.

hi @cscott - I can't seem to get the footer notice showing in patchdemo, nor on beta or testwiki. Apologies but are there specific settings I should have made to test on Patchdemo, and/or an article that i should be testing on?

@mwilliams completed draft recos in this doc (private to design mgrs)

In T363484#10887904, @cscott wrote:

@mwilliams anything learned from the "bit of time next week to explore a couple other possible solutions", or is this design ready to implement?

Adding Apps design folks for visibility and coordinating changes on iOS and Android as needed.

Adding @nayoub @mwilliams to clarify if needed that UX recommendation/expectation has been for a modal (pop-up in iframe) rather than a separate pop-up window. Relevant discussions about the modal preference over pop up window on T364939 and T365298

thanks @Bethany - happy to resolve and track next steps in new tasks as you see fit!

In T391861#10744224, @MatthewVernon wrote:

@RHo can you approve this request, please? Once that's done, this request can proceed.

Adding in @Pginer-WMF as the original designer who likely can speak directly on this. IMO ideally we want one icon for alerts and notices per T142981: Provide a single entry point for notification that anticipates the urgency of the notifications received for desktop as well, but until such time that happens if we are collapsing both alerts and notices under the single bell icon on Minerva, it would make sense for the count to be for the combined unread number.

Adding @nayoub @AAlhazwani-WMF as well for visibility and consideration for overall Contributors design strategy. As part of goals of a more unified, simplified UX for editors, a key design exploration is how might the existing Campaign Updates module in the homepage, which only supports 1 spotlight event by a community be revised and updates to incorporate this more comprehensive, discovery-centered list of many events.

Adding @OTichonova to provide details about requirements from Mod Tools side.

In T373204#10579079, @A_smart_kitten wrote:

For the purposes of task management, if the work here isn’t yet complete, should this task be re-opened? (Alternatively, should another task be opened to track the design review?)

Agree, thanks for checking and re-opening until design is complete!