I just want to check on folks to see if there's any more comments or issues
with this RfC:
https://www.mediawiki.org/wiki/Requests_for_comment/LESS
Basically, this adds a stylesheet preprocessor for ResourceLoader styles
specified as '.less' files; currently no on-wiki or gadget handling is
Ok, we've had another round of review and updates, and it sounds like
people are pretty content with the functionality and the conventions we're
coming up with around LESS usage; and I don't hear many strong objections.
If there's no last-minute surprises from anybody, I'll drop the +2 hammer
on
wrote:
On Sat, Sep 21, 2013 at 10:50 AM, Brion Vibber bvib...@wikimedia.org
wrote:
Ok, we've had another round of review and updates, and it sounds like
people are pretty content with the functionality and the conventions
we're
coming up with around LESS usage; and I don't hear many strong
Reminder to all: this is about to start.
-- brion
On Sun, Sep 22, 2013 at 8:26 PM, Tim Starling tstarl...@wikimedia.orgwrote:
I would like to have an open IRC meeting for RFC review, on Tuesday 24
September at 22:00 UTC (S.F. 3pm).
We will work through a few old, neglected RFCs, and maybe
On Wed, Sep 25, 2013 at 2:53 PM, Chad innocentkil...@gmail.com wrote:
So in the interest of keeping our branches from expanding forever I'm
thinking we should stop creating new branches for each deploy cycle.
What's actually the problem with expanding branches?
Instead, I'm thinking we
On Tue, Oct 1, 2013 at 6:07 AM, Mark A. Hershberger m...@nichework.comwrote:
On 10/01/2013 07:44 AM, Antoine Musso wrote:
The file cache is barely maintained and I am not sure whether anyone
is still relying on it. We should probably remove that feature
entirely and instruct people to
Last I checked I'm making recommendations in an early stage of discussion
on an open mailing list, not making decisions for everybody by myself.
-- brion
On Tue, Oct 1, 2013 at 7:27 AM, Mark A. Hershberger m...@nichework.comwrote:
On 10/01/2013 09:25 AM, Brion Vibber wrote:
We've been
On Tue, Oct 1, 2013 at 9:29 AM, Mark A. Hershberger m...@nichework.comwrote:
Again, I think the best route to go here is to try and gather some real
data from the users of MediaWiki instead of trying to come to a decision
on a mailing list that is populated mostly with developers.
Seems
Question for the group:
Would an officially supported general-purpose MediaWiki hosting service be
useful to people who would like to run wikis, but don't have the time,
expertise, or resources to maintain their own installation?
If so, what can we (as interested parties in MediaWiki development
itching to see something happen on this front
for years. :)
-- brion
- Original Message -
From: Brion Vibber bvib...@wikimedia.org
To: Wikimedia-tech list wikitech-l@lists.wikimedia.org
Sent: Tuesday, October 1, 2013 2:11:16 PM
Subject: [Wikitech-l] Officially supported
On Tue, Oct 1, 2013 at 11:43 AM, Brian Wolff bawo...@gmail.com wrote:
I know this is not your question - but officially supported by whom? I
would consider this massively out of scope for the wmf unless it was using
revenue from this service to subsidize wikipedia. Even then it seems
somewhat
On Tue, Oct 1, 2013 at 12:39 PM, Greg Grossmeier g...@wikimedia.org wrote:
The idea that Brion expressed, I believe, is what we were going for with
the public RFP for the MW Release Management work. It showed community
support and something to point at (by anyone) if a weird decision was
made
On Wed, Oct 2, 2013 at 6:43 AM, Sean Pringle sprin...@wikimedia.org wrote:
However I'd like to hear the historical reasons why MW does everything
binary too.
a) Lack of any native UTF-8 support at all before MySQL 4.1
b) Lack of complete native UTF-8 support until MySQL 5.5.something
Can someone summarize this thread? As far as I can tell someone has
invented a requirement that all features be blessed by the WMF Features
team, and I'm pretty sure that can't be right. Can it?
-- brion
On Oct 3, 2013 12:27 PM, Terry Chay tc...@wikimedia.org wrote:
I am posting this to
So I asked Erik offline for some clarification on this thread, since a
number of people seem worried. To summarize:
* there is no existing or planned rule that WMF Features dept must sign off
on all extensions prior to deployment
* there is no existing or planned rule that WMF Features dept must
TL;DR SUMMARY: check out this short, silent, black white video:
https://brionv.com/misc/ogv.js/demo/ -- anybody interested in a side
project on in-browser audio/video decoding fallback?
One of my pet peeves is that we don't have audio/video playback on many
systems, including default Windows
Out of curiosity, what's an actual example of code where the execution flow
of exceptions is significantly more surprising than the execution flow of a
billion manual checks to avoid Fatal error: Call to a member function
foo() on a non-object?
I've heard the vague claim that exceptions are
of the codebase. I don't think this would
be a particularly useful pattern to follow.
-- brion
On Mon, Oct 7, 2013 at 12:45 PM, Brion Vibber bvib...@wikimedia.org wrote:
Out of curiosity, what's an actual example of code where the execution
flow of exceptions is significantly more surprising than
On Mon, Oct 7, 2013 at 2:45 PM, Erik Bernhardson ebernhard...@wikimedia.org
wrote:
I started replying, but there are just way too many different opinions to
reply to you all. IF the accepted method of handling errors in mediawiki is
to throw an exception and cancel page render we will simply
Woohoo!
I've been doing a lot of code review with Ori lately; he's doing some
awesome work.
Congrats Ori, and welcome to the hotseat. :)
-- brion
On Tue, Oct 8, 2013 at 11:59 AM, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone,
I'm excited to announce that Ori Livneh will be moving
Commons mobile app updates are in staging now...
Wikimedia Commons for Android 1.0beta12 should appear in Google Play within
a few hours. It can also be installed directly from
http://dumps.wikimedia.org/android/wikimedia-commons-1.0beta12.apk
Android version includes various smaller bug fixes,
I believe there was a configuration error this morning which got some
redirects stuck in cache; they should be on the way to being fixed...
-- brion
On Tue, Oct 22, 2013 at 11:56 AM, Eugene Zelenko
eugene.zele...@gmail.comwrote:
Hi!
I experienced weird problem today when accessing Commons
On Thu, Oct 24, 2013 at 10:01 AM, Élie Roux
elie.r...@telecom-bretagne.euwrote:
This title is around 90 Tibetan characters, but each caracter being 3
bytes, it exceeds the limit for title length of 256 bytes that MediaWiki
has.
So I have two questions:
1. If I change this limit to 1023 in
On Fri, Oct 25, 2013 at 8:19 AM, Daniel Barrett d...@vistaprint.com wrote:
Search around for '255' appearing in .php, .inc, or .js files and change
the checks to 1023. [...]
Should someone maybe define a constant Title::MAX_LENGTH instead of
hard-coding 255 in many PHP files?
Yes, such a
So I'll just make a few brief, general points:
* It might be nice for the design folks to weigh in here with their
thoughts on font selection.
* We traditionally didn't specify a lot of fonts at all, meaning you got
whatever default fonts were configured on your system: thus, non-free fonts
like
Saying that the people who picked the font stack should be able to defend
their selection of font stack and their ability to design for all customers
with it isn't avoiding the question; it's sending the question to the ONLY
people who can sensibly answer it.
Keep in mind that a) the design team
Generally I would not recommend subclassing User; while you can certainly
create such a subclass it will have limited utility as you can't really
control how they get created easily.
Like the rest of MediaWiki, the User class is intended to be customized
through extension hooks... What sort of
I think a better way to go is to add a hook point in
RecentChange::checkIPaddress()... I don't like mixing more session-related
stuff into User like a getUserIP method.
-- brion
On Oct 27, 2013 2:46 PM, Marcin Cieslak sa...@saper.info wrote:
Brion Vibber bvib...@wikimedia.org wrote
On Mon, Oct 28, 2013 at 4:00 AM, Brian Wolff bawo...@gmail.com wrote:
[snip]
it would probably be safer to just totally
disable method arguments in the stack trace for the web output only leaving
the method names. Imo that would still give enough useful info (a good
percentage of the time the
We're churning through some internal discussion with legal on if and how
how this affects our potential options...
Note that the specific thing announced there doesn't include a licensed AAC
*audio* codec which would be required to generate audio and video+audio
files playable on current browsers
Hear, hear!
There's a cake in the office, hopefully someone can upload him a piece. :D
-- brion
On Thu, Oct 31, 2013 at 2:52 PM, MZMcBride z...@mzmcbride.com wrote:
Happy Tim Starling Day! :-)
It seems this year is the tenth anniversary:
Woohoo! Everybody prepare your bugs and feature reqs for bite-sized work
units!
-- brion
On Friday, November 1, 2013, Quim Gil wrote:
Wikimedia is one of the ten organizations selected to participate in
Google Code-in 2013! This means that on November 18 we will start having
hundreds of
On Mon, Oct 28, 2013 at 3:25 PM, Jon Robson jdlrob...@gmail.com wrote:
I would suggest not discussing Deprecating inline styles.
I actually think it should be closed [1]
Can we discuss this one [2] instead ?
[1]
On Fri, Nov 1, 2013 at 3:02 PM, Quim Gil q...@wikimedia.org wrote:
Scheduled proposed:
Wednesday, November 6, 2013 at 10:00 PM UTC
(2:00 PM in SF, Thu 9:00 AM in Sidney)
On Sat, Nov 2, 2013 at 12:35 AM, Tyler Romeo tylerro...@gmail.com wrote:
On Fri, Nov 1, 2013 at 5:41 PM, Matthew Flaschen mflasc...@wikimedia.org
wrote:
So this does not change anything in my view.
Actually it changes something pretty important. This means that now all
major browsers
On Mon, Oct 7, 2013 at 9:01 AM, Brion Vibber bvib...@wikimedia.org wrote:
As an experiment, I've built Xiph's ogg, vorbis, and theora C libraries
cross-compiled to JavaScript
[snip]
Performance on iOS devices isn't great, but is better with lower
resolution files :)
I've also started
as architects should be meaningful, and if so, how to expand it
beyond the original triumvirate (Brion, Tim Mark), e.g. by
transitioning to a community-driven process for recognizing
architects.
Hi all,
in March 2011 and June 2011, Brion Vibber, Mark Bergsma and Tim
Starling were announced as Lead
On Wed, Nov 6, 2013 at 7:54 AM, Chad innocentkil...@gmail.com wrote:
How about we make editbugs self-granting? That is, if you've got editbugs
you can give it to others (like we did with Coder a few years ago). It
works
pretty well, scales infinitely, and tends to protect itself against
On 11/06/2013 02:33 AM, Quim Gil wrote:
Do the three architects consider themselves assuming this role as WMF
employees or as community members?
For myself -- I've been a Wikipedia MediaWiki community contributor since
long before there was a Wikimedia Foundation. I still think of WMF as
The WebRTC IETF working group will be making a codec selection decision
(VP8 vs H.264) today -- the meeting is open to participation via XMPP chat
(Google Talk appears to work) and there will also be a live audio stream
from the in-person room.
(WebRTC is the peer-to-peer media connection
different vendors.
And of course audio and video tags also still have no mandatory minimum
codec support, so status quo reigns supreme in HTML5 video with
incompatible browser implementations. Awesome!
-- brion
On Thu, Nov 7, 2013 at 12:47 PM, Brion Vibber bvib...@wikimedia.org wrote:
The WebRTC
As folks may be aware, over in the Wikimedia Mobile Apps team we're
starting a refresh of the Wikipedia mobile apps for Android and iOS, which
have not been updated in a while and are now wayyy behind the mobile web in
features and UI awesomeness.
The new apps are using native UI around the
Is there a list of proposals already submitted? I definitely want there to
be a session on XWiki's embedded file viewer/editor widget proposal
http://www.webviewers.org/xwiki/bin/view/Main/WebHome if there's not
already one... worse case I'll just file a couple of redundant entries. :D
-- brion
to allow offline reading... Exciting times!
* Android: http://dumps.wikimedia.org/android/apps-android-wikipedia
-dev-sprint2.apk
* iOS: on testflightapp.com (email notifications sent to our recently
trimmed beta list)
On Wed, Nov 20, 2013 at 6:33 PM, Brion Vibber bvib...@wikimedia.org wrote
Perhaps I am a dumbass, but where is the gitblit link on:
https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend
which the sort of link you get from the Projects list on gerrit?
I cannot find it.
-- brion
On Wed, Dec 11, 2013 at 10:48 AM, Chad
, Brion Vibber bvib...@wikimedia.org
wrote:
Perhaps I am a dumbass, but where is the gitblit link on:
https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend
which the sort of link you get from the Projects list on gerrit?
I cannot find it.
-- brion
Filed as http://code.google.com/p/gerrit/issues/detail?id=2335
-- brion
On Wed, Dec 11, 2013 at 11:15 AM, Brion Vibber bvib...@wikimedia.orgwrote:
So the pages that get you *to* the project page have links to the actual
source browser, but the project detail page doesn't. Brilliant.
I'll
mirrors (they'll end
up in Gerrit in the long run), and please don't be afraid to come talk to
us in #wikimedia-mobile on Freenode IRC. We don't bite! Much.
-- brion
On Wed, Dec 4, 2013 at 4:38 PM, Brion Vibber bvib...@wikimedia.org wrote:
Second work sprint on the new apps is wrapping up
Yes, this would be a pretty straightforward addition to the mw.Title object
or something that accepts one as a filename similarly.
https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Title_objects
Like the 'fileExists' this might be marked as an 'expensive' operation
since
Offhand I'd say use bcrypt, but from http://us3.php.net/password_hash --
*Caution*
Using the *PASSWORD_BCRYPT* for the *algo* parameter, will result in the
*password* parameter being truncated to a maximum length of 72 characters.
This is only a concern if are using the same salt to hash strings
Indeed, mobile is traditionally the land of terrible latency, so that's a
great place to concentrate effort. :)
On touchscreen devices of course we don't have hover events as such, but we
could do predictive preloading on touchstart, then trigger the load action
on touchend.
False positives that
TLD proliferation is a scam by money-hungry registrars who want people to
register (and thus pay) in multiple TLDs to protect their brands.
I recommend we boycott/ignore these various things and just avoid them, but
I know we're going to end up registering a bunch for the brand protection
I've taken the liberty of enabling[1] lower-resolution .ogv video
transcodes, at 360p and 160p in addition to the 480p we already generated.
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=61690
These will be useful for older or slower or mobile machines which need to
use non-native software
the player to
handle this case better.
-- brion
On Fri, Feb 21, 2014 at 6:07 AM, bawolff bawolff...@gmail.com wrote:
On Thu, Feb 20, 2014 at 7:07 PM, Brion Vibber bvib...@wikimedia.org
wrote:
[..]
Files should gradually populate at the smaller sizes as they get
referenced
and the new
, Brion Vibber bvib...@wikimedia.org wrote:
TL;DR SUMMARY: check out this short, silent, black white video:
https://brionv.com/misc/ogv.js/demo/ -- anybody interested in a side
project on in-browser audio/video decoding fallback?
One of my pet peeves is that we don't have audio/video playback
We bumped the releases back to make them more awesome (and include login
basic editing features in the first big release). Few more weeks. :)
-- brion
On Sat, Feb 22, 2014 at 10:22 PM, Yuvi Panda yuvipa...@wikimedia.orgwrote:
On Sat, Feb 22, 2014 at 4:50 AM, Greg Grossmeier
21, 2014 at 10:37 AM, Brion Vibber bvib...@wikimedia.orgwrote:
In addition to the sudden burst of transcodes, we found that the player
widget is sometimes aggressively selecting the small size when it should be
defaulting to a larger size.
So we're temporarily disabling the small sizes again
Chrome beta (version 34) now includes native 'srcset' support:
http://www.chromestatus.com/features/4644337115725824
This means that on high-density screens like a Retina MacBook Pro, the 1.5x
or 2.0x-size image will be loaded automatically by the browser, and our
JavaScript hack disables itself.
Thanks for doing this research!
I notice that while Liberation Sans got a high score for appearance, it got
a very low technical score... Since it is a FOSS project
https://fedorahosted.org/liberation-fonts/ we should attempt to file bug
reports with Red Hat about any problems we discover,
On Sun, Feb 23, 2014 at 6:43 AM, Brion Vibber bvib...@wikimedia.org wrote:
Just an update on this weekend project, see the current demo in your
browser[1] or watch a video of Theora video playing on an iPhone 5s![2]
[1] https://brionv.com/misc/ogv.js/demo/
[2] http://www.youtube.com/watch?v
On Thu, Mar 6, 2014 at 2:08 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 4:15 PM, Steven Walling steven.wall...@gmail.com
wrote:
If your patch causes a serious UX regression like this, it's going to get
reverted. The core patch involved was being deployed to Wikimedia
On Thu, Mar 6, 2014 at 3:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Is there anything specific in the communications involved that you found
was problematic, other than a failure to include a backlink
Latest Wikimedia-internal iOS build on TestFlight -- anyone working for
Wikimedia who wants to test but didn't get the email please let me know and
I'll get you set up. Currently we can only do internal beta distribution
for iOS, but we hope to be able to do wider testing again soon.
Public
I spent a little more time the last few weekends on ogv.js
(JavaScript-based player for Ogg Theora and Vorbis media in IE and Safari)
and have gotten two major things working:
* an all-Flash version -- should work in older IE and Safari versions that
can't run the JS code
* optional GPU
There've been some issues reported lately with image scaling, where
resource usage on very large images has been huge (problematic for batch
uploads from a high-resolution source). Even scaling time for typical
several-megapixel JPEG photos can be slower than desired when loading up
into something
On Thu, May 1, 2014 at 3:54 AM, Gilles Dubuc gil...@wikimedia.org wrote:
_don't consider the upload complete_ until those are done! a web uploader
or API-using bot should probably wait until it's done before uploading
the
next file, for instance...
You got me a little confused at
Hertzlich willkommen Bernd!
-- brion
On May 12, 2014 10:09 AM, Tomasz Finc tf...@wikimedia.org wrote:
Bernd will be working remotely from Fort Collins, CO, where he has
lived ever since emigrating from Germany many years ago.
He joins the Wikimedia Foundation after developing software at HP
From my read, SplEnum is a bit janky -- you still have to defibe integer
constants and may have to pass them in.
The proposal here is more php-natural in that you can say Month::$JANUARY
similarly to how you'd use Month::JANUARY, whereas SplEnum recommends the
more verbose new
I tend to agree that skins should be installed in exactly the same way as
other extensions. This will also help make installation more automateable.
-- brion
On May 20, 2014 11:39 PM, Tim Starling tstarl...@wikimedia.org wrote:
On 21/05/14 07:25, Bartosz Dziewoński wrote:
*
On Wednesday, June 11, 2014, Martijn Hoekstra martijnhoeks...@gmail.com
wrote:
Thank you very much for the interesting talk, everybody. I do have a follow
up question though, that I didn't think of during the talk. It was
indicated that the glyphs will occupy the private use space. Many
That X-Range header was an experiment me and Faidon tried for the ogv.js
media player I've been prototyping (Flash fallback version) . We couldn't
get the extra header -- or the regular Range header -- to work through the
varnish layer though, so current code doesn't use it.
Its safe to remove
On Sat, Jul 5, 2014 at 11:23 PM, Brian Wolff bawo...@gmail.com wrote:
On 7/6/14, Brion Vibber bvib...@wikimedia.org wrote:
That X-Range header was an experiment me and Faidon tried for the ogv.js
media player I've been prototyping (Flash fallback version) . We couldn't
get the extra header
Ideally, the tests would also compare expected output intelligently -- IIRC
the parser tests still just use a fairly simple string comparison and even
things like whitespace or attribute order that make no effect on the
behavior of the HTML output get marked as differences. (This is also why we
On Friday, July 11, 2014, Risker risker...@gmail.com wrote:
This is one of those perennial proposals that never quite seems to take
off; I can remember having some version of this discussion back in 2008,
and I know that some of our earliest edits show a partially obscured IP
address, not the
I've started experimenting with embedding my ogv.js media player into
TimedMediaHandler to provide Ogg playback in Safari and Internet Explorer:
https://gerrit.wikimedia.org/r/#/c/145756/
This involves on-demand loading of a fairly large chunk of mostly
machine-generated, dense, pre-minified
I spent the weekend hacking at integration of my ogv.js JavaScript Ogg
media player into TimedMediaHandler's embedded player widget. Patch set in
progress:
https://gerrit.wikimedia.org/r/#/c/145756/
It's pretty much working in Safari 7 and IE 10/11, but needs various tweaks
and fixes still. Some
AM, Brion Vibber bvib...@wikimedia.org
wrote:
I spent the weekend hacking at integration of my ogv.js JavaScript Ogg
media player into TimedMediaHandler's embedded player widget. Patch set
in
progress:
https://gerrit.wikimedia.org/r/#/c/145756/
It's pretty much working in Safari 7
On Sun, Jul 13, 2014 at 9:31 PM, Brion Vibber bvib...@wikimedia.org wrote:
https://gerrit.wikimedia.org/r/#/c/145756/
Here's a wiki running the patch with some sample files:
https://ogvjs-testing.wmflabs.org/
Status update:
* Resolution switching is now available
* Automatic selection
I would probably recommend using the existing EventLogging infrastructure
for sending the data to our back end, assuming it won't explode under heavy
load spikes... Which it might. :)
-- Brion
On Jul 24, 2014 3:14 PM, Gergo Tisza gti...@wikimedia.org wrote:
Hi all,
frontend development is
I believe the point is to actively work on *doing* the third party support.
This does not require an Organization or Community *unrelated* to all
of us here talking on this list, but does require people with particular
common interests to communicate and act together for their common benefit.
As
Woohoo!
-- brion
On Aug 5, 2014 6:54 PM, Ori Livneh o...@wikimedia.org wrote:
(apologies for cross-posting)
On either Thursday or Friday of this week, Giuseppe Lavagetto (of the
Wikimedia TechOps team) and I are planning to migrate
https://test.wikipedia.org/ (testwiki) to HHVM. The way
Well if we kill off XML and other funky formats we can call it the JSON
API :)
-- brion
On Thu, Aug 7, 2014 at 11:00 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Thu, Aug 7, 2014 at 10:58 AM, David Gerard dger...@gmail.com wrote:
but if you are a mobile developer using the
Agreed; mobilefrontend and mobilefrintend-tests would probably work as
a pair, same with cirrus etc. however the list of roles is getting kinda
long and may need a better display with descriptions and search in the
future... If we add lots more extensions *and* their optional tests or
configs it's
There's been some recent controversy over access to control over site JS
which I'd prefer not to wade into... but it does remind me of some ideas
I've been mulling over related to sandboxed JavaScript execution.
Power users need to have an easy way to write, deploy, and use tools that
integrate
On Thursday, August 14, 2014, Sumana Harihareswara suma...@wikimedia.org
wrote:
Summary and logs now up:
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-08-13#Summary_and_logs
Andrew Russell Green is the new CentralNotice Caching Overhaul - Frontend
Proxy point person.
On Wed, Dec 5, 2012 at 11:53 AM, Chad innocentkil...@gmail.com wrote:
On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper aklap...@wikimedia.org
wrote:
bugzilla.wikimedia.org is operational again and is now running the
latest stable version (4.2.4, before was 4.0.9).
There's been some idle
Since the switch from OggHandler to TimedMediaHandler we are one step
closer to supporting video on mobile browsers.
In fact, there's one it works in now -- Firefox for Android!
We've been able to close out this Firefox evangelism bug about our broken
mobile video:
Over on the mobile team we've been chatting for a while about the various
trade-offs in native vs HTML-based (PhoneGap/Cordova) development.
Currently our main Wikipedia apps are all HTML-based:
* Android - HTML + Cordova + plugins
* iOS - HTML + Cordova + plugins
* BlackBerry PlayBook (and later
We've gone a bit off topic into the question of whether we should spend any
time on mobile at all, it seems. :)
On Dec 11, 2012 5:11 PM, MZMcBride z...@mzmcbride.com wrote:
I think I fundamentally agree with your point, but when I consider that
there is (for example) no API for adding or
On Thu, Dec 13, 2012 at 10:38 AM, Brion Vibber bvib...@wikimedia.orgwrote:
On Wed, Dec 12, 2012 at 2:50 PM, Rob Lanphier ro...@wikimedia.org wrote:
I was able to play the WebM file of the locomotive on the front page
of https://commons.wikimedia.org just now on my Nexus 7 using Chrome,
so
On Thu, Dec 13, 2012 at 2:56 PM, Brion Vibber bvib...@wikimedia.org wrote:
I can play the current media on the front page of Commons in Chrome on my
Nexus 7, but it won't play in position on either desktop
http://en.wikipedia.org/wiki/Serge_Haroche or mobile
http://en.m.wikipedia.org/wiki
On Thu, Dec 13, 2012 at 4:38 PM, Michael Dale md...@wikimedia.org wrote:
I think this relates to the page not being purged after the transcodes are
updated. If you purge the page, will probably give the nexus a more
playable flavour.
On Wed, Dec 26, 2012 at 11:47 AM, Mono monom...@gmail.com wrote:
Could we add support for Twitter cards in Wikimedia projects? It wouldn't
be hard to do and would would be really nice for articles, images, videos -
everything linked from Wikimedia on Twitter could have a nice little
preview
On Wed, Dec 26, 2012 at 12:25 PM, Sébastien Santoro
dereck...@espace-win.org wrote:
On Wed, Dec 26, 2012 at 9:16 PM, Brion Vibber br...@pobox.com wrote:
On Wed, Dec 26, 2012 at 11:47 AM, Mono monom...@gmail.com wrote:
We should also double-check on appropriate goodies for Facebook and other
On Sat, Dec 29, 2012 at 6:41 AM, Nischay Nahata nischay...@gmail.comwrote:
I could find a method to covert a timestamp into the user preferred
timezone in the Language class; Looks like the wrong place to me.
Is there any other way (think global function) to convert to the user's
timezone and
On Tue, Jan 22, 2013 at 2:53 PM, Ct Woo ct...@wikimedia.org wrote:
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
migrate the database masters over from Tampa to
On Wed, Jan 23, 2013 at 10:11 AM, Chad innocentkil...@gmail.com wrote:
Hi,
There's been a lot of bikeshedding topics recently. On things ranging
from spaces, to typos, to naming things. I was kind of tired of these
mundane threads, so I decided to start one on something productive.
What
On Wed, Jan 30, 2013 at 12:29 PM, Quim Gil q...@wikimedia.org wrote:
On 01/30/2013 10:43 AM, Amir E. Aharoni wrote:
* Page 9 - Consider mentioning Firefox OS in addition to Android and
iOS. Brion and Patrick already poked in that direction. (And well,
it's a FLOSS conference, but since you
On Wed, Jan 30, 2013 at 11:42 PM, Zaki Akhmad zakiakh...@gmail.com wrote:
On Thu, Jan 31, 2013 at 5:35 AM, Brion Vibber br...@pobox.com wrote:
Indeed our primary focus is on Android and iOS right now, as we're a
small
team and that's where the users are.
I just installed Wikipedia iOS ap
On Feb 2, 2013 1:45 PM, Platonides platoni...@gmail.com wrote:
Your system does not seem to support OGG audio format. Downloading this
file without ogg support may need a significant amount of space and
bandwith. Downloading article.wav ... 20%
Something tells me that won't be feasible for
1 - 100 of 1208 matches
Mail list logo
