Dan awesome! Glad there is some interest - this should be a lot of fun! :-)
On Wed, Mar 5, 2014 at 1:20 PM, Quim Gil <qgil(a)wikimedia.org> wrote:
> fyi
>
>
> -------- Original Message --------
> Subject: [WikimediaMobile] Zurich Hackathon: Creating a map namespace
> Date: Wed, 5 Mar 2014 12:54:52 -0800
> From: Jon Robson <jdlrobson(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, mobile-l
> <mobile-l(a)lists.wikimedia.org>
>
> This may be extremely ambitious, but I'm keen to kick off development
> around the creation of a map namespace during the Zurich hackathon.
>
> The goal would be to setup an editable map namespace that could be
> used for a variety of things, one of which would be adding a map view
> to the Special:Nearby page provided via the mobile site. The goal is a
> proof of concept not necessarily anything production ready (but that
> would be great if we could get to that point!)
>
> Please let me know if you would also be interested on hacking such a
> thing -
> https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Geo_Namespace
> - or if doing so would be a terrible idea (but if you have to go down
> that route please provide constructive reasoning on what would be a
> less terrible idea)
>
> Excited to hack on cool things in Zurich!
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
>
--
Jon Robson
* http://jonrobson.me.uk
* https://www.facebook.com/jonrobson
* @rakugojon
+mobile-l
Greetings. Rupert, an update!
The rebooted Android (Android 2.3+) and iOS (iOS 6+) apps will have
Wikipedia Zero flourishes built into them, making it possible for the user
to know whether the app access is free of data usage charges. The rebooted
apps are tentatively slated for store submission at the end of the month.
The flourishes will hinge on each operator's zero-rating of HTTPS.
Likewise, HTTPS contributory features are about to be introduced on the
Wikipedia Zero mobile web experience as well for operators that zero-rate
HTTPS.
WMF is starting the work with partner operators to add support for
zero-rating of HTTPS. There will be, at least, technical hurdles
(networking equipment architecture varies) in this transition, but it's
underway! Indeed, we have some carriers that have noted support for HTTPS
zero-rating already.
I'm very much grateful to Brion, Yuvi, and Monte for their assistance while
I added code to the Android and iOS platforms, and am happy to get to work
with them more while putting final touches in place this month. Props to
Faidon, Mark, and Brandon in Ops Engineering as well on helping us overcome
some rather non-trivial hurdles in order to retain good performance and
maintainability while adding HTTPS support.
-Adam
On Mon, Aug 26, 2013 at 3:34 PM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> On Mon, Aug 26, 2013 at 8:19 AM, Adam Baso <abaso(a)wikimedia.org> wrote:
>
> > Rupert, I saw your question regarding Wikipedia Zero. Wikipedia Zero is
> > currently targeted for the mobile web, but I'll take this question back
> to
> > the business team as to whether we'd be able to support zero-rating of
> apps
> > traffic at some point in the future, at least in locales where moderate
> > bandwidth is available.
> >
>
> I think that once the zero-rating is switched to support HTTPS by using
> IP-based instead of Deep Packet Inspection-based HTTP sniffing, ISP
> partners wouldn't actually be able to distinguish between mobile web and
> mobile apps content unless we actively choose to make them use separate IPs
> and domain names.
>
> Especially if, as we think we're going to, the future Wikipedia mobile app
> will consist mostly of native code widgets and modules that plug into the
> web site embedded in a web control... it'll be loading mostly the same web
> pages from the same servers, but running a different mix of JavaScript.
>
> -- brion
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
The mobile team met today to discuss potential focus areas for the
Zurich hackathon
You can find our rough notes here
http://etherpad.wikimedia.org/p/MobileZurchHackathon
For those volunteers coming by do let us know what you would like us to cover
Were eager to help make your extension mobile ready as we get closer
to a world where 50% of our traffic is mobile.
--tomasz
The Mobile App team had their monthly retrospective today. Notes and
action items are below.
https://www.mediawiki.org/wiki/Wikimedia_Apps/imported/Retrospective-March_…
Action items include
* sign-off availability [kenan]
* Not enough people looking at the app (and doubly so for Android?) [kenan]
* experiment with bug-report built in feature on ios [mhurd]
* Not enough comments and discussion on the design trello board+++ [team]
* tried to give moiz the link for release but it didn't seem to work
for him [mhurd]
We really need more help with Android and iOS testers. Who's up for
the challenge of building and refining the best native reading and
editing Wikipedia experience on mobile?
--tomasz
So late last night a patch got merged in core which had the knock on
effect of creating a bad experience on mobile. The change basically
notified a user if their username was adjusted e.g. uppercased or
spaces removed. Since most mobile device input fields default to
lowercase rather than Titlecase, this means that pretty much anyone
who now tries to register an account on mobile will see a warning that
their username has been capitalized and will have to fill in the
registration form again (yikes!)
I reverted the offending change for the time being
https://gerrit.wikimedia.org/r/#/c/117234/
but according to Greg the branch has been cut and it will now need to
be backported.
It would be good if we can get this lightning deployed so that this
doesn't effect account creation numbers on mobile.
Anyone able to help out here?
This may be extremely ambitious, but I'm keen to kick off development
around the creation of a map namespace during the Zurich hackathon.
The goal would be to setup an editable map namespace that could be
used for a variety of things, one of which would be adding a map view
to the Special:Nearby page provided via the mobile site. The goal is a
proof of concept not necessarily anything production ready (but that
would be great if we could get to that point!)
Please let me know if you would also be interested on hacking such a
thing - https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Geo_Namespace
- or if doing so would be a terrible idea (but if you have to go down
that route please provide constructive reasoning on what would be a
less terrible idea)
Excited to hack on cool things in Zurich!
Maps and Geo community members. I've put together a proposal to build
a new team at the WMF that I'd love your feedback on.
Take a pass on
https://www.mediawiki.org/wiki/Wikimedia_Engineering/Maps_%26_Geo_Team
and let me know what you think on the discussion page. I'd especially
like your help on the possible projects we could focus on with a key
eye on contributions.
--tomasz
*(Resending, got stuck in pending queue for size.)*
Here's a trendline for about one month of usage.
https://commons.wikimedia.org/wiki/File:Wikipedia_Zero_One_Month_WML_Percen…
The figure seems to be holding between 0.2% and 0.3% for that most recent
1-month period of available WML usage data in Wikipedia Zero.
Other content types are not counted in this WML percent; for example, the
following hits on <language>.(m|zero).wikipedia.org are excluded: JSON,
XML, PNGs, icons, JavaScript and CSS. Furthermore, content served from
domains such as upload.wikimedia.org (media, including most article images)
andbits.wikimedia.org (frequently accessed core UX elements such as
JavaScript, CSS, icons, etc.) is not part of the denominator.
The previous email referring to sub-0.1 percent WML /hit/ ratios on
in-scope active carriers - for which I provided some rather basic analysis
- holds. However, using the re-worked definition of WML percent described
here there's a slightly higher skew.
In addition to the PDF trendline, a quick and dirty look at the 20140214
log for active operators shows the following rough layout.
Less than 0.5% WML
Overall traffic in this zone is 77.03% of the W0 traffic; average of 0.05%
WML in-zone
Between 0.5% and 1.35% WML
Overall traffic in this zone is 22.73% of the W0 traffic; average of 1.08%
WML in-zone
Between 1.35% and 4.9999999999% WML
Overall traffic in this zone is 0.22% of the W0 traffic, average of 2.07%
WML in-zone;
5% and higher WML
Overall traffic in this bucket is 0.015% of the W0 traffic, average of
34.2% WML in-zone
The percents don't add to 100 perfectly as a consequence of rounding.
Generally, WML seems to be in decline across most Wikipedia Zero operators,
but there are some exceptions (e.g., one operator's WML percent as defined
here seems to be holding steady around 1% with this definition of WML,
although I'm sort of skeptical of whether the user agent is actually
WML-only or even a mobile device or is incapable of handling HTML).
We're analyzing whether WML deprecation has a disparate impact measurable
enough to defer exclusive concentration on HTML, especially in light of the
increasing availability of cheap mobile devices supporting HTML and the
tendency for large intermediary search services and appliances to translate
HTML to WML on behalf of the actual client device in the rare case of a
device only supporting WML.
-Adam
On Fri, Feb 28, 2014 at 12:41 PM, Yuri Astrakhan
<yastrakhan(a)wikimedia.org>wrote:
> I just ran some stats on the 1/1000 sample logs for ZERO traffic. Due to
> nature of Zero - to bring Wikipedia to the developing world - we have to
> deal with lots of old phones. I would like to reopen WAP discussion before
> we put the final nail into the coffin or decide if this data warrants
> further investigation.
>
On 01.03.2014, 0:41 Yuri wrote:
> I just ran some stats on the 1/1000 sample logs for ZERO traffic.
> Due to nature of Zero - to bring Wikipedia to the developing world -
> we have to deal with lots of old phones. I would like to reopen WAP
> discussion before we put the final nail into the coffin or decide if
> this data warrants further investigation.
Wow, that UA parser managed to miss even a few iPhones!:) If we throw
them away along with other stuff we know (Symbian, NetFront,
Blackberries, newish Nokia and Samsumg feature phones) we will
essentially have only MAUI and Dorado left. Currently we're mostly
serving them HTML because they claim they support it in their Accept
headers.
Examples:
User-agent: 'MAUI WAP Browser'
Accept: 'text/vnd.wap.wml,application/vnd.wap.xhtml+xml,application/xhtml+xml,image/vnd.wap.wbmp,image/gif,image/jpg,image/jpeg,image/bmp,text/html,*/*;q=0.1'
User-agent: 'Dorado WAP-Browser/1.0.0/powerplay/2'
Accept: 'text/vnd.wap.wml,application/vnd.wap.xhtml+xml,application/xhtml+xml, image/vnd.wap.wbmp, image/gif, image/jpg,image/jpeg, image/png, image/bmp, text/html,*/*;q=0.1'
From this, we can conclude that people with these browsers keep using
Wikipedia which indicates that their browsers can actually digest our
HTML view. And even if they didn't, there are very good reasons not to
keep maintaining WML support:
* We don't actually serve valid WML: http://i62.tinypic.com/27zxa14.png ,
and making it valid would be quite a task.
* Our WML support is severely bitrotten and will remain this way
unless we continuously spend time on it.
* Spending engineers' time on something with usage share as small will
take resources away from much more important goals of improved
reading experience and contributory features for vast majority of
our readers. And we've neved had too much resources.
--
Best regards,
Max Semenik ([[User:MaxSem]])
