Oops, sorry I missed that :p At least we've got it scheduled now for next
iteration.
On Wed, Mar 12, 2014 at 11:14 AM, Jon Robson wrote:
> Arthur if you look 2 replies up you'll see I did :)
> https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1757
>
> On Wed, Mar 12, 2014 at 11:09
Arthur if you look 2 replies up you'll see I did :)
https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1757
On Wed, Mar 12, 2014 at 11:09 AM, Adam Baso wrote:
> If you happen to pursue this card, it's implicit, but was hoping you could
> tag in the disposition of whether it's W0-scop
If you happen to pursue this card, it's implicit, but was hoping you could
tag in the disposition of whether it's W0-scoped or not. The flag in the
data should be generic, like "w0" if it's W0.
On Wed, Mar 12, 2014 at 10:58 AM, Arthur Richards
wrote:
> Jon, create a story card for this and we ca
Jon, create a story card for this and we can discuss a bit during today's
planning meeting.
On Wed, Mar 12, 2014 at 10:30 AM, Jon Robson wrote:
> Exactly.
>
> According to click tracking the settings page gets 200 clicks a day
> (compared to Watchlist which gets around 5K) - although note this
Exactly.
According to click tracking the settings page gets 200 clicks a day
(compared to Watchlist which gets around 5K) - although note this
clicktracking is only limited to users of high end phones (requires
JavaScript). I think these metrics would be very useful to have and
would let us get a
You're talking about having the origin servers take POSTs and make a
backend event logging call, right? As opposed to a pure JavaScript event
logging solution. I believe that doing it with origin servers hitting event
logging would be ideal for ensuring that data is captured for both devices
withou
Poke.
I'm no sure if it's safe to add a new data point, but I'd love to know
the answer to this question. Alternatively we could use EventLogging
on the server side to log people that disable images (as well as those
that opt in and out of beta). I think it's a useful component to have
on mobile es
Good question. I think we'd need to log this origin side, and look at
percentage usage on mdot in general and usage percentage on mdot for
Wikipedia Zero and see the results and see if there's any measurable
difference.
Is it safe to add this data point via MobileFrontend's existing
DOMParse wfDeb
One concept we've toyed with is adding a "Text only" hyperlink at the top
of the articles for access via mdot for Wikipedia Zero traffic only; the
"text only" version would of course needs it hyperlink at the top to say
"Turn images on". In either case, we haven't done this to date as I recall
beca
Adam, I am interested in who uses the feature "Images" on
Special:MobileOptions which sets a cookie disabling images. I'm not
sure how page views to Special:MobileOptions is related. Is it
possible to see % of page views where the "disableImages" cookie is
set? This would give a better indication o
Based on the 20140302 W0 logfile it looks like Special:MobileOptions
constitutes about 1% of "pageviews" (not the bulletproof definition, but a
good enough one).
On Mon, Mar 3, 2014 at 11:04 AM, Tomasz Finc wrote:
> We added it specifically for Zero back in the day. Should be easy
> enough to m
We added it specifically for Zero back in the day. Should be easy
enough to measure and get into a sprint.
On Mon, Mar 3, 2014 at 10:35 AM, Jon Robson wrote:
> On this page - https://en.m.wikipedia.org/wiki/Special:MobileOptions -
> it is possible to disable images across the mobile site.
>
> How
On this page - https://en.m.wikipedia.org/wiki/Special:MobileOptions -
it is possible to disable images across the mobile site.
How many people actually use this (outside Zero)? Can we get some data?
I personally think we should explore killing this feature as an option
and leave it to the browse
13 matches
Mail list logo
