Flagging my comment here: T333473#8740476 because it feels like the reveal functionality should be an additional task.

Just a note for, @Niharika + @Tchanders.

Generally the beta cluster has always been a problematic testing location for the apps since whilst it strives to, that cluster doesn't replicate production in a consistent manner, and for many experiences its simply just broken and its not something that apps engineering can rely on to support this work.

My understanding is that this feature wouldn't be enabled in production until much later this year with a fairly short turn around time aimed for between enabling in places like testwiki / test2wiki and enabling more broadly elsewhere.

iOS and Android have done some initial investigations but there are some technical risks that we aren't able to fully assess.

The most challenging issues are that:

• Our suggested edits functionality rely on a web of interaction between commons, wikidata and wikipedia via API's. We only provide this to logged in users but we will want to verify temporary accounts interact with this accounts correctly.
  • At minimum can we enable this extension on more wiki's on the beta cluster.
  • This won't solve everything as it is made more complicated by the fact that beta commons is pretty broken. Images don't render and looks like structured data on commons there isn't currently functioning.
  • The maintainers, structured data, are also head down on grant work that takes priority at the moment so I don't know when or if they expect to work on ip masking work.
• Production is currently the only place that supports push notifications.
  • Could deployment to test.wikipedia.org / test.wikidata.org occur earlier, even in some limited form? This would probably allow us to verify with much much much more certainty both for the above issues and this one?

Thanks for this @Seddon - we also have a need to test on testwiki, since a lot of our changes are in CheckUser. We're currently working out an estimate for when we can deploy to testwiki (and which one), so will update you on this in a couple of weeks when @Niharika is back.

In T329913#8873702, @Tchanders wrote:

Thanks for this @Seddon - we also have a need to test on testwiki, since a lot of our changes are in CheckUser. We're currently working out an estimate for when we can deploy to testwiki (and which one), so will update you on this in a couple of weeks when @Niharika is back.

Awesome thanks @Tchanders!

From Dmitry: deep dive into IP masking on the Beta cluster (i.e. fully integrating the app with it, and making sure things work) https://docs.google.com/presentation/d/1uThBQetCKWD7XEL1RMK3cJ2RvhlQIxGGvC4RigCHkAY/edit#slide=id.gb558081a57_0_50

In T329913#8873703, @Seddon wrote:

In T329913#8873702, @Tchanders wrote:

Thanks for this @Seddon - we also have a need to test on testwiki, since a lot of our changes are in CheckUser. We're currently working out an estimate for when we can deploy to testwiki (and which one), so will update you on this in a couple of weeks when @Niharika is back.

Awesome thanks @Tchanders!

@Tchanders and @Niharika just a ping to check in on timing for this. Design work is starting to come together for both iOS and Android and we could do with having this in place to be able to kick off engineering work

In T329913#8939120, @Seddon wrote:

In T329913#8873703, @Seddon wrote:

In T329913#8873702, @Tchanders wrote:

Thanks for this @Seddon - we also have a need to test on testwiki, since a lot of our changes are in CheckUser. We're currently working out an estimate for when we can deploy to testwiki (and which one), so will update you on this in a couple of weeks when @Niharika is back.

Awesome thanks @Tchanders!

@Tchanders and @Niharika just a ping to check in on timing for this. Design work is starting to come together for both iOS and Android and we could do with having this in place to be able to kick off engineering work

Apologies about a late response. The latest timeline is to deploy on testwiki in early January 2024 and start with pilots tentatively in March. We are somewhat flexible so if it takes the Apps teams longer to get the changes in we can delay the pilot deploy (as needed).