Sat, Jan 19
Fri, Jan 18
Yes, that is done in the page library.
The page library could detect if the content language is Asian and then chose a smaller minimum, let's say 20 or even lower (any suggestions?).
Thu, Jan 17
Maybe we could use randomInCategory, get a bunch of descriptions for the list of articles, and pick 3 most similar ones that are not exactly the same?
Yes, that's what I want. I had already included the module name mediawiki.skinning.content.parsoid in my previous request. Then I was now wondering why the .mw-image-border rules didn't get included in my version of the request.
After trying changing various query parameters to get them closer to your request I suspect that it was the useskin=minerva that triggers it. I had only skin=minerva before. Going that route changes other parts of the CSS that leads to undesired side-effects:
- The font is now a serif font instead of sans-serif.
- Infobox content is not centered anymore and has white background instead of gray.
@Tgr The search probably failed because the string had line breaks in the source.
The Swagger UI is taken from RB. The one for 1.3.0 and later is summary_new.yaml. The summary.yaml file in RB is for 1.2.0.
Wed, Jan 16
Deployed 30 minutes ago.
Not sure what column to put this one but it's not really actionable from our side at this time, so I'm going to put it in tracking.
@Niedzielski The possible values for the type field are listed in https://www.mediawiki.org/wiki/Specs/Summary/1.3.0:
"standard", "disambiguation", "no-extract", "mainpage"
https://www.mediawiki.org/wiki/Page_Previews/API_Specification doesn't mention "generic" either. Not sure where that was coming from.
@Jdlrobson I think we're going to want the content.parsoid.less styles included in Minerva as well for this to properly work? Thoughts?
Tue, Jan 15
content.parsoid.less styles are already requested but not included in the response of https://en.wikipedia.org/w/load.php?debug=false&lang=en&skin=minerva&target=mobile&only=styles&modules=ext.cite.style%7Cext.math.styles%7Cext.pygments%7Cext.timeline.styles%7Cmediawiki.page.gallery.styles%7Cmediawiki.skinning.content.parsoid%7Cmobile.app%7Cmobile.app.parsoid%7Cskins.minerva.base.reset%7Cskins.minerva.content.styles.
Fri, Jan 11
Setting priority to low since the backend work for this seems quite complicated and the workaround of using MW API seems sufficient currently.
Wed, Jan 9
Tue, Jan 8
ActionCounters, since it's for the edit action feed?
Wed, Jan 2
If this is for all pages then that could turn out quite expensive on the server side.
The links in the task description point to empty pages. Anyone know some good examples of links to glossary pages?
What API is needed here?
Dec 19 2018
Assuming this is CI doing this, hence moving to tracking. Feel free to move to our backlog if that is incorrect.
Dec 17 2018
Dec 14 2018
Oh, you're right. Never mind.
@cooltey I think you don't need to set uselang. uselang is only for message translations, like user visible strings. Error messages and such AFAIU. You could set it to user or content, according to the help text in https://www.wikidata.org/wiki/Special:ApiSandbox.
Dec 13 2018
Yes, noimages can be removed now.
Dec 12 2018
Not sure what's going on there. +1 to @Pchelolo statement about /page/random/title using MW API. It's using the random generator to request 12 random pages and finds the most interesting page title of the dozen results. We did not deploy any new code around this timeframe. During the last week or two we deployed code which should actually reduce pressure on the event loop, and still continuing to do so. this week.
Dec 7 2018
Shouldn't @Jdforrester-WMF be added, too?
Dec 5 2018
@schoenbaechler We can deploy this change today.
action=mobileview is still used by the apps, and by MCS (for the main pages).
Dec 3 2018
@Pcheclolo I was thinking the new PCS endpoint would call the corresponding Parsoid endpoint (internally).
I wonder if we should do something similar to https://en.wikipedia.org/api/rest_v1/#!/Transforms/post_transform_wikitext_to_html_title_revision and use the same as the backend service, just run the transformations on top of it.
Nov 28 2018
I hope the project page on mediawiki.org with relevant information also includes:
- an architecture overview showing the major components. I know there's a queue involved. What are the other parts, etc.?
- links to repo(s)
- anything useful for debugging
- how to solve/investigate typical issues
Nov 26 2018
FWIW, looks broken even when RESTBase usage is turned off. In https://en.wikipedia.org/api/rest_v1/page/mobile-html/Fraction_(mathematics) this text looks better, though. So, I think it's probably something on the app side.
Nov 21 2018
App devs/QA, please test the announcements. You'll have to ignore the date and may have to override the country. (There are dev settings for the Android app to do so. I don't know if the iOS app has a similar setting.)
Nov 20 2018
Nov 19 2018
@Mholloway Ok, that makes sense. It's a bit annoying to have to open the section with the actual text, too. So, it's not a clear cut improvement over the desktop URL. I'm fine leaving it as is then.
Now checking the URLs, I think we should consider using the mobile (.m) version of the donation policy link.
Yes, my bad. Had tested PS6 instead of PS8. Now it looks much better:
There are some issues with the image being large and cropped:
The above is on an old Nexus 5 in portrait mode. In landscape it's marginally better but still too big and a little bit cropped.
@Nirzar I'm not sure what the best way to handle this is. This will affect web a little bit, too, at least by bloating up the CSS. So, I thought it's best to ask for advice first.
Thanks, @schoenbaechler. I haven't diffed the various versions of the body texts but it looks to me that the only difference between the countries are the country names, coffee price, and average donations, like we had last year. Is this correct? Last year we used some server side templating to insert those variables. Also we'll change the text to be HTML (turn the formatting into HTML tags).
Nov 14 2018
Looks like this rule only exists for Vector. Our base CSS endpoint requests Minerva, though: https://en.wikipedia.org/w/load.php?debug=false&lang=en&skin=minerva&target=mobile&only=styles&modules=ext.cite.style%7Cext.math.styles%7Cext.pygments%7Cext.timeline.styles%7Cmediawiki.page.gallery.styles%7Cmediawiki.skinning.content.parsoid%7Cmobile.app%7Cmobile.app.parsoid%7Cskins.minerva.base.reset%7Cskins.minerva.content.styles
The Parsoid HTML actually doesn't have this attribute to begin with. Instead it wraps the <a><img> into a <figure-inline class="mw-image-border">.
Nov 13 2018
Nov 10 2018
In this article the references template comes at the end of the lead section:
Nov 8 2018
Nov 7 2018
Getting the day of the week from the announcement text is problematic since we don't know what time zone the client is in, e.g. Australia vs UK. I think the day of the week should come from the client based on the local time zone.
Nov 5 2018
Nice. Not that it makes a big difference but instead of caching at the parsoid-access._getRestPageContent() level you could also do it at api-util.restApiGet().
We've been able to create flame graphs with:
npm install -g autocannon clinic clinic flame --on-port='autocannon -c1 http://localhost:6927/en.wikipedia.org/v1/page/mobile-sections/Cat' -- node server.js
Nov 2 2018
Oct 31 2018
@Mholloway Have you produced any flame graphs? Anything worth sharing in regards to that?
Oct 29 2018
I think there is a benefit of doing I18N in the PCS layer instead of the wikimedia-page-library since then the page library wouldn't have to bundle the translatable strings. I'm going to change the task title and description accordingly. (OTOH we could also split up the wikimedia-page-library into a client bundle and a server bundle.)
Oct 25 2018
Oct 22 2018
I'm glad you found a solution for this. But CC'ing Reading Infrastructure for more visibility.
@Charlotte No updates yet. Is this something that's blocking you? In any case I've moved this to Upcoming so it hopefully gets picked up earlier.