+wikitech-l
This sounds like something that might be good for the newly forming
multimedia team to work on. As Yuvi pointed out (off the wikitech-l list):
"There are also unresolved codec issues with playing videos (no H264
support), so even if we do enable video playback it'll not be
available everywhere, and even in places where it is it is going to be
a biggish battery sink (no hardware decoding support). Would want to
consider that before enabling it fully."
I envision the mobile team helping to support this, but folks who focus on
multimedia-related stuff would probably be the best candidates for digging
into this and figuring out how we can best move forward.
On Thu, Jun 20, 2013 at 6:16 PM, Jon Robson <jdlrobson(a)gmail.com> wrote:
> I would like to see videos working on mobile
>
> Yet there seems to be two issues here.
> 1) Cleaning up MobileFrontend code
> We are stripping the ogg_player by parsing and cleaning up the HTML
> We could probably do this in css/javascript instead.
>
> 2) Making videos work on mobile where supported
> If we were to explore enabling videos on mobile we would have to look
> at the ogg player javascript code associated with it and get it
> working on mobile or create our own code that knows how to read it.
> http://www.mediawiki.org/wiki/Extension:OggHandler
>
> I'm also concerned about the size of the javascript module and since
> it is not needed by every page I would argue that it should only be
> loaded when the video is clicked (the existing extension may do this
> or not I'm not clear):
>
> https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FOggHandler/895f74e6…
>
>
> On Thu, Jun 20, 2013 at 5:35 PM, Max Semenik <maxsem.wiki(a)gmail.com>
> wrote:
> > Hi, when mobile WP was in its childhood, it was decided that we're not
> > ready to display videos on our pages, so they were stripped. And
> > stripped very crudely, by removing just #ogg_player_1 and
> > #ogg_player_2 so that only first two videos on a page were removed.
> > What are your opinions - shoudld we continue doing this?
> >
> >
> >
> > --
> > Best regards,
> > Max Semenik ([[User:MaxSem]])
> >
> >
> > _______________________________________________
> > Mobile-l mailing list
> > Mobile-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
>
> --
> Jon Robson
> http://jonrobson.me.uk
> @rakugojon
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
I've just found out that WMF's Bugmeister Andre Klapper removed "nearly
everyone"'s Bugzilla adminship (and people with root access on the servers
now have access to a file which contains login details for an 'emergency
admin' account). So I have some questions:
* Who was removed?
* Who still has access?
** Is the list on https://meta.wikimedia.org/wiki/System_administrators still
up to date?
Also please ban the account of the user who created
https://bugzilla.wikimedia.org/show_bug.cgi?id=50029
Alex Monk
Welcome to the latest edition of the weekly deployment highlights!
The full schedule for next week is at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_June_17th
= Monday =
* MediaWiki 1.22wmf7 will go out to all non-Wikipedia project sites (eg:
Wiktionary, Wikisource, Wikinews, Wikibooks, Wikiquote, Wikiversity,
and a few other sites)
= Tuesday =
* ULS (Universal Language Selector) will be enabled on the following
wikis:
** Portuguese (pt), Chinese (zh), Vietnamese (vi), Ukrainian (uk),
Catalan (ca), Waray-Waray (war), Norwegian (Bokmål) (no), Cebuano
(ceb), Finnish (fi), Persian (fa)
* On Tuesday VisualEditor team will enable an A/B test, where half of
new accounts created on English Wikipedia will get VisualEditor
enabled by default. This is to test performance and features before
the larger rollout in July.
= Thursday =
* MediaWiki 1.22wmf7 will go out to all Wikipedias
* MediaWiki 1.22wmf8 will go out to test/test2/mediawiki
If you have any questions, please do let me know!
Have a good weekend,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I posted a message on 10-June-2013 and Yuri followed up with one last week.
But in case anyone missed it, a Wikipedia Zero RFC for use of Edge Side
Includes (ESI) and, where appropriate, JavaScript is posted at
https://www.mediawiki.org/wiki/Requests_for_comment/Zero_Architecture#Cache…
.
We'd like to wrap up comments within the next few days.
Thanks!
-Adam
+wikitech-l
On Mon, Jun 24, 2013 at 11:37 AM, Brion Vibber <bvibber(a)wikimedia.org>wrote:
> On Thu, Jun 20, 2013 at 5:35 PM, Max Semenik <maxsem.wiki(a)gmail.com>wrote:
>
>> Hi, when mobile WP was in its childhood, it was decided that we're not
>> ready to display videos on our pages, so they were stripped. And
>> stripped very crudely, by removing just #ogg_player_1 and
>> #ogg_player_2 so that only first two videos on a page were removed.
>> What are your opinions - shoudld we continue doing this?
>>
>
> So, here's the thing -- we've dropped OggHandler and switched to
> TimedMediaHandler which outputs its markup differently -- the new system is
> not stripped by MobileFrontend!
>
> Videos used in the wikis today actually output a <video> element pointing
> by default to a WebM source. These *actually work* in Chrome and Firefox
> on Android... but iOS and other non-Android systems will generally not have
> WebM support and will show a "broken video" placeholder.
>
> We're still kinda talking internally about license issues for H.264
> support... whee
>
> -- brion
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Since nobody reads mobile-l
---------- Forwarded message ----------
From: Jon Robson <jdlrobson(a)gmail.com>
Date: Sat, Jun 8, 2013 at 4:17 AM
Subject: [WikimediaMobile] Number crunching: Upload errors on mobile
To: mobile-l <mobile-l(a)lists.wikimedia.org>
I ran some data crunching on a sample of 4429 photo uploads from
mobile web. In this sample 2821 uploads succeeded and 36% (1608/4429)
of attempted uploads failed. This is very high and unacceptable.
Looking closely 53% of all errors were due to problems with invalid or
'anonymous' tokens. This will occur when the client is unable to get a
token using CORS from Commons due to not being logged in there.
Luckily Chris Steipp and the rest of the platform team have pushed a
change that should significantly reduce this error:
https://gerrit.wikimedia.org/r/#/c/57662/
CentralAuth related errors (861)
####################################
Anonymous token. 598
Invalid token 263
The next big offender was 'Missing filename' accounting for 22% of all
upload errors. Unfortunately this is ambiguous as it could mean a
variety of things - it simply means that an upload was attempted and
the response didn't report the filename. I've pushed a patch to try to
understand what errors we are running into:
https://gerrit.wikimedia.org/r/67545
Other errors (467)
###################################
Missing filename 347
This file did not pass file verification 69
Blank error message given 36
The file you submitted was empty 15
There are various other errors all listed below for your enjoyment.
Some due to bad choices of name, permissions problems and attempts to
upload certain file types we do not accept. The good news is we
probably don't want these uploads to succeed as they hint at vandalism
attempts or uploads by poorly educated users.
The server problems section is worth a look though - although a small
percentage "The modification you tried to make was aborted by an
extension hook 61". These errors are occurring on the following wiki
projects:
* sv.m.wikipedia.org
* de.m.wikipedia.org
* test.m.wikipedia.org
* en.m.wikipedia.org
* ar.m.wikipedia.org
* es.m.wikipedia.org
* ja.m.wikipedia.org
* he.m.wikipedia.org
* fr.m.wikipedia.org
* nl.m.wikipedia.org
Any ideas what may be causing that error?
***
Other errors:
Users uploading with bad or unclear filenames (113)
####################################
"titleblacklist-custom-filename" 48
(https://commons.m.wikimedia.org/wiki/Template:Titleblacklist-custom-filenam…)
"titleblacklist-forbidden-edit" 37
(https://en.m.wikipedia.org/wiki/MediaWiki_talk:Titleblacklist-forbidden-edit)
Filename exists 25 (I suspect they used a common filename)
Unknown error: "titleblacklist-custom-double-apostrophe" 3
(Out of interest is there any API to check whether a filename will be accepted?)
Server problems (81):
####################################
The modification you tried to make was aborted by an extension hook 61
Database query error 10
An internal error occurred 9
error: Internal Server Error 1
Permission based errors (69)
####################################
The "autoconfirmed" right is required to edit this page 36
You have been blocked from editing 25
The "protect" right is required to edit this page 7
Unknown error: "globalblocking-ipblocked" 1
(These users should not be seeing the upload button!)
Users uploading with bad file types (17):
###########################################
Filetype not permitted: MOV 8
Filetype not permitted: webp 4
Filetype not permitted: mp3 3
Filetype not permitted: xml 1
Filetype not permitted: bmp 1
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
--
Yuvi Panda T
http://yuvi.in/blog
Hello all,
Due to the US holiday next week (Independence Day, July 4th) on
Thursday, we have decided to delay the RFP selection announcement by one
week. You can now expect to hear something the week of July 8th.
The end of the community feedback period is still the same (this
Wednesday, June 26th) to give us time to review and discuss.
Thank you for your understanding,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I'm supposed to help write a blog post on this at some point, but I
wanted to follow Tyler's comment and say that from my perspective, and
a few other people in the WMF, I'd like to see several more volunteers
in the security process. We need more people doing design reviews,
secure code reviews, fixing security bugs, etc.
I think it's mostly been an organic process in the past, but I'd like
to be more intentional and systematic about getting contributors
trained and get them access to things like the security bugs in
bugzilla, so we can have more eyes on the issues and make sure new
features support the direction we're headed for security. If you have
+2 on core, and have reported or fixed some security bugs, I'll
probably be reaching out to you over the summer to see if you're
interested in getting more involved. But if anyone else is interested,
feel free to get in touch with me and I'll make sure you're included
on that list.
On Sat, Jun 22, 2013 at 9:52 PM, Tyler Romeo <tylerromeo(a)gmail.com> wrote:
> I'd also like to know this information. Being a Bugzilla admin and helping
> out with the bug workflow and security issues and whatnot has always been
> something I've wanted to do. But if the WMF is trying to consolidate for
> some reason...
>
> *-- *
> *Tyler Romeo*
> Stevens Institute of Technology, Class of 2016
> Major in Computer Science
> www.whizkidztech.com | tylerromeo(a)gmail.com