Mobile-l May 2015

mobile-l@lists.wikimedia.org

41 participants
43 discussions

Start a nNew thread

(no subject)
by Tara Thompson 15 May '15

15 May '15

please sending messages Sent from Yahoo Mail on Android

1 0

WG: [Wikitech-l] Tracking Antifeature?
by florian.schmidt.welzow＠t-online.de 15 May '15

15 May '15

FYI Best, Florian -----Original-Nachricht----- Betreff: [Wikitech-l] Tracking Antifeature? Datum: Fri, 15 May 2015 01:41:32 +0200 Von: Ricordisamoa <ricordisamoa(a)openmailbox.org> An: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> FYI https://f-droid.org/wiki/index.php?title=org.wikipedia&diff=54674 https://f-droid.org/wiki/page/Antifeature:Tracking _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Android Wikipedia beta app release
by Michael Holloway 15 May '15

15 May '15

Hello, I'd like to invite you to check out the newest version of Wikipedia Beta, which will be available shortly on Google Play. Changes in the latest version include: * Add Link Preview dialog for some users * Handle image map links in-app * Make sure Share A Fact button works on all devices * Fix sharing of images to Facebook app * Increase "tap to expand" click area * Remove "read next" prototype * Fix text directionality consistency in Nearby * Show "Read in other languages" only if article exists in other languages * Fix language picker word wrap * Add upside-down mode for newer devices * Hide caption on "tap to expand" table when open Enjoy! Michael

2 1

[iOS][Apps] Wikipedia Mobile 4.1.3 for iOS
by Corey Floyd 15 May '15

15 May '15

Hey everyone… The latest for iOS is live on the app store. You can download it here: https://itunes.apple.com/us/app/wikipedia-mobile/id324715238?mt=8 We are continuing our quest to squash bugs and tighten up the screws, but you’ll see a few new features in there as well. This also represents our 3rd release in just over a month after a nearly 4 month drought - our release pipeline in full effect! Automated builds + Crash Reporting + Phabricator Tasks FTW! Please check it out if you get a chance and let us know what you think - mailing list, in app feedback, or an app store review - all are appreciated! Thanks for reading! -- Corey Floyd Software Engineer Mobile Apps / iOS Wikimedia Foundation

3 2

Reader's Watchstar habits
by Jon Robson 14 May '15

14 May '15

MobileWebWatching schema has been active for some time now, I'm happy to now reveal the results: These are the number of clicks to the watchstar per funnel across the site in stable: page 61627 watchlist 1635 search 3105 nearby 279 and across all mobile modes: page 63928 nearby 333 search 3357 watchlist 1890 As can be seen traffic to watchstars outside the current page is low. I would suggest we therefore stop showing the watch star in search, nearby results and Special:EditWatchlist and just focus on the funnel from the page itself. If interested I generated this data using: select event_funnel, count(*) from MobileWebWatching_11761466 group by event_funnel It's also worth pointing out 8,025/12,964 ([1,2]) of the unique users using the watch star had an edit count of 0. [1] select count(distinct event_userId) from MobileWebWatching_11761466 where event_mobileMode = 'stable' [2] select count(distinct event_userId) from MobileWebWatching_11761466 where event_mobileMode = 'stable' and event_userEditCount = 0

1 0

Hackathon: mobile apps meeting needs?
by Adam Baso 14 May '15

14 May '15

Hi all - Quim asked if there are meeting needs for the Lyon hackathon for mobile apps at https://phabricator.wikimedia.org/T92272 . Please do coordinate with Quim on that ticket as appropriate and update https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015/Mobile_apps accordingly. Thanks. -Adam

5 11

Re: [WikimediaMobile] [Analytics] killed a lot of queries on analytics-store
by Adam Baso 13 May '15

13 May '15

3 3

Knowledge Transfer on MaxSem's API / Extension Work to Reading
by Adam Baso 13 May '15

13 May '15

Hi all - Max Semenik, now on Search & Discovery (he's been working on geo stuff for a while), spoke with me earlier today about transferring Reading-oriented extension components / API endpoints off his plate. I'll add the bullet points to the Etherpad for the recurring APIs/Services meeting instance tomorrow. * API action=mobileview : the apps are heavy users of this endpoint. * pageimages extension: Max noted that the algorithm needs improvement for targeting the "best" image. * featuredfeeds extension (RSS/Atom) * TextExtracts is still an open question. Max said he can maintain it in maintenance mode, if necessary. But if there's interest in Reading taking over future work on this, that would be even better. Max noted the persistence of the results is an area for improvement. Incidentally, some people have been communicating about this stuff today. Thanks. -Adam

3 3

Removing upload interface code from MobileFrontend
by Jon Robson 13 May '15

13 May '15

A while back we disabled the mobile uploads interface in mobile. It's been sitting in our codebase dormant so people can enable it via user js if necessary but it's broken a few times and doesn't seem to be getting the attention it needs. Given there is now an editing team and from what I understand UploadWizard is being refactored into oojs ui (which will lead to it being less bulky and more mobile friendly) I'd like to suggest we abandon the code in MobileFrontend and help support that effort. Note this effort is likely to take a long long time, since that extension suffers from much technical debt and makes use of jquery ui, which is not available on mobile, so to set expectations we're not going to be in a state where we can enable this on mobile (if we wanted to which again is highly questionable) any time soon (think in units of a year rather than weeks/months). The downside of this is any 3rd parties who are using this uploads code (it's turned on by default) will lose this feature and there is no available alternative. I've written a patch to remove it [1] but I just wanted to post this here to give people the chance to voice any concerns/disagree with this approach. Note: We can always restore the code later on if necessary. I argue this will be easier than fixing/maintaining the existing code. Someone could also put it into a separate extension if they wanted to use it. See also: https://phabricator.wikimedia.org/T97169 [1] https://gerrit.wikimedia.org/r/#/c/210084/

7 8

"Flag for later" in Phabricator's Maniphest
by Joaquin Oltra Hernandez 12 May '15

12 May '15

Hi, Kaldari asked yesterday on irc what the "Flag for later" button does on a task on Maniphest. After a few minutes of confusing googling (you can imagine the freaking button appearing in thousands of bugs with the button...) I found that it is like a favourites list, personal and hidden, with color coded categories. Go to https://phabricator.wikimedia.org/flag/ while logged in and you will see the items you have flagged for later. Not sure what to use it for, but for example I've flagged a bug I created that I was having difficulty finding everytime, for easy access. If you think of other use cases or actually are using it for something, it would be great to know. Cheers.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l May 2015