In case you didn't know, all API calls support 2 caching parameters,
"maxage" and "smaxage". The first one controls client caching (basically
sends headers back that will make the client cache the request), the second
one controls server caching (varnish) across users. If you use the latter
for thi
+mobile-l
On Fri, Jun 5, 2015 at 11:23 AM, Adam Baso wrote:
> Okay to move this to mobile-l?
>
>
> On Friday, June 5, 2015, Brian Gerstle wrote:
>
>> While they strip out links/citations, they do preserve text formatting
>> (italics & bold).
>>
>> On Fri, Jun 5, 2015 at 10:39 AM, Bernd Sitzman
Thanks. Want me to reach out to Amazon about that crash condition so they
can patch it?
On Friday, June 5, 2015, Dmitry Brant wrote:
> +mobile-l
>
>
> On Fri, Jun 5, 2015 at 11:23 AM, Adam Baso > wrote:
>
>> Okay to move this to mobile-l?
>>
>>
>> On Friday, June 5, 2015, Brian Gerstle > > wrot
Sure! When I highlight the word "London", the Wikipedia preview contains an
IPA block that has a link which, when pressed, causes the app to crash.
On Fri, Jun 5, 2015 at 11:27 AM, Adam Baso wrote:
> Thanks. Want me to reach out to Amazon about that crash condition so they
> can patch it?
>
>
>
I would guess they are using the extracts. It returns pretty clean html
with the content.
For example:
https://en.wikipedia.org/w/api.php?action=query&prop=extracts&format=jsonfm&exintro=&titles=plebeian&redirects=
You can also request plain text
https://en.wikipedia.org/wiki/Special:ApiSandbox
Cross posting. See follow up discussion on analytics list web archive.
-- Forwarded message --
From: *Dan Andreescu*
Date: Friday, June 5, 2015
Subject: [Analytics] Pageview API Status update
To: Analytics List
I just posted a comment on the famous task:
https://phabricator.wik
Message sent.
On Friday, June 5, 2015, Dmitry Brant wrote:
> Sure! When I highlight the word "London", the Wikipedia preview contains
> an IPA block that has a link which, when pressed, causes the app to crash.
>
>
> On Fri, Jun 5, 2015 at 11:27 AM, Adam Baso > wrote:
>
>> Thanks. Want me to re
Thanks for this email Adam. It took me some time to get to it :p
Just a little note regarding MobileFrontend. We are planning work to make
it thinner and better versioned, and strip certain responsibilities outside
of it and properly test them, like for example the mobileview API.
What I want to
FWIW, they are also doing basically the same thing in the e-ink hardware
Kindles.
On Fri, Jun 5, 2015 at 8:25 AM, Dmitry Brant wrote:
> +mobile-l
>
>
> On Fri, Jun 5, 2015 at 11:23 AM, Adam Baso wrote:
>
>> Okay to move this to mobile-l?
>>
>>
>> On Friday, June 5, 2015, Brian Gerstle wrote:
>
