We're focused on other goals right now for Q1 but this is important and should be looked into.

We should discuss changing the implementation to Wikidata lexemes and the implications in a new task, to figure out the coverage compared to wiktionary.

@Pchelolo Do you know the frequency of the errors? To help us prioritize how urgent it is to fix.

Hey @Mholloway, can you tag the appropriate teams and add a description with links and what we need, with some approximate wanted date of deployment?

@Tsevener are you tweaking it to output different HTML or to output structured data?

Moving to tracking until it is QAd.

Just as a reminder, Toni mentioned:

From grooming:

@MSantos can you have a look and let us know if the priority should be higher?

I chatted with @JoeWalsh and we discussed a few things related to this:

page/summary is also consumed on web on every link preview so the output needs to be kept small if possible.

Re: Open questions, it seems like the JSON blob is quite big, so embedding it in the HTML may have implications for the time to interactive on the browser. Scraping it from the HTML is doable and it shouldn't necessarily cause repaints/reflows that would impact performance, but it may take a chunk of main thread UI time. I'm not sure if that would have an impact on the user's interactions with the webview.

@ssastry It seems like we don't have anything specific to do for this. Please re-open if there is anything you will require us to tackle for the switch.

Based on what Rita mentioned on the doc, it seems to me that they are using the media wiki api that I posted above (they count the last 60 days), instead of the REST api.

There is also the mediawiki API pageviews prop where you can batch a number of titles on the same request and get other things from the mediawiki api if you want while you are at it: https://en.wikipedia.org/wiki/Special:ApiSandbox#action=query&format=json&prop=pageviews&titles=Banana%7CPhone%7CApple&formatversion=latest

Closing then.

@Mholloway @bearND Do we have specific questions or needs? As far as we discussed this will happen transparently through restbase and there will be no breaking changes so we should be good.

We are going to have to re-plan how to approach that goal, so will have discussions in other venues I think.

I don't think this is needed AFAIK. And if we were to start adding metadata somewhere it would be in the metadata endpoint not on the summary one. 👎 declined

@Mholloway why is this on needs analysis? Does it need fleshing out?

mobile-html url: https://zh.m.wikipedia.org/api/rest_v1/page/mobile-html/%E6%97%A5%E6%8A%A5

I've cleaned up the last remaining open tasks in the project.

On some small wikis, the featured article doesn't change every day. Could be weekly or monthly.

This can be a big task. Besides documenting all of those, we should think about how we are going to approach the different wikis to add the classes or HTML attributes to their documentation pages, like what happened with the IPA template change not long ago.

Declined for now.

Ping @JoeWalsh, should we dig into this more, or decline? Seems like the service was developed and deployed with apps just fine a long time ago.

I saw! Good writing :D

Once we figure out how to move forward with this taking into account Bernd's comments above, we can update the description and move this to the backlog or upcoming.

@ovasileva This is probably a bug on mobile web too?

I'll re-link to the very much related post series we did last year, that does a deep dive in to this kind of workflow with Extension:Popups:

Done!

@bearND Mind moving the subtasks related to this that you are working on to the kanban board instead of this one? I made it an epic based on your comment in T217837#5022095

We should understand if we have to update our code to get descriptions better from the SDC project.

@bearND Is this fixed, should we resolve?

@bearND to move under the appropriate epic and prioritise.

@bearND to move under the appropriate epic and prioritise. This could be blocked on figuring out how the app injects settings to the web view.

@bearND to move under the appropriate epic and prioritise. This could be blocked on figuring out how the app injects settings to the web view.