Hi, I'd like to present a new RFC for your consideration:
https://www.mediawiki.org/wiki/Requests_for_comment/Minifier
It is about how we can shave 10-15% off the size if JavaScript
delivered to users.
Your comments are highly welcome!:)
--
Best regards,
Max Semenik ([[User:MaxSem]])
When api.php was basically the only API in MediaWiki, calling it "the API"
worked well. But now we've got a Parsoid API, Gabriel's work on a REST
content API, Gabriel's work on an internal storage API, and more on the
way. So just saying "the API" is getting confusing.
So let's bikeshed a reasonably short name for it that isn't something awful
like "the api.php API". I'm horrible at naming.
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
Thank you for the quick fix!
Best,
--
Sukyoung
On Jan 29, 2014, at 9:55 AM, Nathan wrote:
> FYI in case you aren't subscribed to the list.
>
> ---------- Forwarded message ----------
> From: Yair Rand <yyairrand(a)gmail.com>
> Date: Tue, Jan 28, 2014 at 7:25 PM
> Subject: Re: [Wikitech-l] Bug in the Wikipedia main web page
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> Thank you for pointing out this bug. Your suggested change to
> MediaWiki:Gadget-wm-portal.js has been implemented by Meta-Wiki
> administrator User:PiRSquared17.
>
>
> On Tue, Jan 28, 2014 at 6:50 PM, Sukyoung Ryu <sukyoung.ryu(a)gmail.com>wrote:
>
> > Dear all,
> >
> > We are researchers at KAIST in Korea working on finding JavaScript bugs in
> > web pages. While analyzing top websites from Alexa.com, we found an issue,
> > which seems to be a bug, on the Wikipedia main web page (wikipedia.org).
> > We would be grateful if you can either confirm that it is a bug and even
> > better fix it or let us know what we're missing.
> >
> > Here's the issue. When a user selects a language in which search results
> > are displayed via the language selection button from the Wikipedia main web
> > page, the following JavaScript function is executed:
> >
> > 1 function setLang(lang) {
> > 2 var uiLang = navigator.language || navigator.userLanguage, date
> > = new Date();
> > 3
> > 4 if (uiLang.match(/^\w+/) === lang) {
> > 5 date.setTime(date.getTime() - 1);
> > 6 } else {
> > 7 date.setFullYear(date.getFullYear() + 1);
> > 8 }
> > 9
> > 10 document.cookie = "searchLang=" + lang + ";expires=" +
> > date.toUTCString() + ";domain=" + location.host + ";";
> > 11 }
> >
> > Depending on the evaluation result of the conditional expression on line
> > 4, "uiLang.match(/^\w+/) === lang", the function leaves or dose not leave
> > the selected language information on the user's computer through a cookie.
> > But we found that the expression, "uiLang.match(/^\w+/) === lang", always
> > evaluates to false, which results in that the function always leaves
> > cookies on users' computers. We think that changing the contidional
> > expression, "uiLang.match(/^\w+/) === lang", to the expression,
> > "uiLang.match(/^\w+/) == lang", will solve the problem.
> >
> > This problem may occur in the main web pages of all the Wikimedia sites.
> > Could you kindly let us know what you think? Thank you in advance.
> >
> > Best,
> > Changhee Park and Sukyoung Ryu
> >
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
Hi all,
My apologies if this is the wrong place to start a discussion on this, but
it's a better place than nowhere. I recently took part in two very
different Wikipedia workshops -- one in Uganda for schoolchildren aged
14-17, and one Bodø, Norway, for GLAM people aged 35-55. One glaringly
obvious barrier of entry that was common for both groups is that the
CAPTCHA we use is too freaking hard.
The main concern is obviously that it is really hard to read, but there are
also some other issues, namely that all the fields in the user registration
form (except for the username) are wiped if you enter the CAPTCHA
incorrectly. So when you make a mistake, not only do you have to re-type a
whole new CAPTCHA (where you may make another mistake), you also have to
re-type the password twice *and* your e-mail address. This takes a long
time, especially if you're not a fast typer (which was the case for the
first group), or if you are on a tablet or phone (which was the case for
some in the second group).
So I would like to start a discussion about changing to a CAPTCHA that is
more user-friendly, and hopefully one that isn't as
English/Latin-alphabet-centric as the one we currently use. If Ugandan
children and old Norwegian people, which all use the Latin alphabet, have
such problems deciphering the CAPTCHA, what about people speaking languages
that don't use the Latin alphabet? I would prefer something more
simplistic, like some sort of math or image-based CAPTCHA, instead of the
current CAPTCHA we use.
--
mvh
Jon Harald Søby <http://meta.wikimedia.org/wiki/User:Jon_Harald_S%C3%B8by>
Please join us for the following tech talk:
*Tech Talk**:* What's New with MediaWiki-Vagrant?: Simple Use Cases and
Beyond
*Presenter:* Bryan Davis & Dan Duvall
*Date:* November 25th
*Time:* 1830 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=What%27s+New+with+…>
Link to live YouTube stream <http://www.youtube.com/watch?v=I66xR-fq2O8>
*IRC channel for questions/discussion:* #wikimedia-office
Google+ page <http://www.youtube.com/watch?v=I66xR-fq2O8>, another place
for questions
*Talk description:*We'll start off by giving a brief refresher on how
MW-Vagrant works and how it differs from stock Vagrant. Next, we'll
showcase some of the newest and most useful features of MWV such as
multi-wiki support, SSH/HTTP sharing, Labs integration, advanced
customization using Hiera and local roles. Finally, we'd like to show how
MWV can be useful in test-driven development by demonstrating how to run
unit and browser tests. The last 15 minutes will be reserved for Q/A.
== Outline (WIP) ==
* (10 minutes) What is Vagrant, MediaWiki-Vagrant, Puppet (dan + bryan)
* (15 minutes) Local customizations (bryan)
* (15 minutes) Running unit tests and browser tests under MW-V (dan)
* (5 minutes) Vagrant sharing (it's awesomesauce!!!) (bryan)
* (15 minutes) Q & A
Hi all,
I've had a significant update to Live Preview in the pipeline for a while now. It brings a few major improvements, the most important of it being able to load resourceloader modules that the preview requires, fixing a whole slew of problems that the old implementation had. The only place where it is a bit limited is with regard for previewing the list of languages in in skins other than vector.
The code is here: https://gerrit.wikimedia.org/r/#/c/131346/ <https://gerrit.wikimedia.org/r/#/c/131346/>
And it could use some user testing and review.
Some people have been asking me about this lately, so I figured time to strip the WIP tag of it and see if we can get this merged already.
Long term, I would like to improve it to make use of mw.template for some of the elements, but that is not a necessity right now I think.
DJ
I am pleased to announce Andrew Garret joining the Wikimedia
Foundation as a full time Software Engineer
Andrew has been contracting with the Wikimedia Foundation for over six
years now and its only fitting to announce that now that he's done
with his studies he'll be going full time at the Wikimedia Foundation.
In the past six years, he's worked on a huge variety of projects,
ranging from user preferences and spam filtering to notifications and
two attempts to fix talk pages. He's passionate about making people’s
workflows and processes make sense, so in the coming months, he's
looking forward to having the time and energy to focus on software
that humanizes our projects, eliminates busy work, and makes life
easier for new and old contributors.
Right now Andrew is in the process of moving from Sydney to Maastricht
to be with his girlfriend
He'll be working from Maastricht; and from early next year, Prague.
So if you find yourself in one of those cities, you should let him know!
When not working, doing assignments, or packing bags, Andrew is busy
travelling or homebrewing.
He's currently supporting the Flow team and we're exploring where
he'll help next.
Please join me in celebrating Andrew going full time
--tomasz
Hello,
I am not sure this is the right mailing list to introduce this project
but I have just released Displee. It is a small Android app that allows
to search for images in the English Wikipedia by taking pictures:
https://play.google.com/store/apps/details?id=org.visualink.displee
It is a kind of open source Google Goggles for images from en.wikipedia.org.
I have developed Displee as a demonstrator of Pastec http://pastec.io,
my open source image recognition index and search engine for mobile apps.
The index hosted on my server in France currently contains about 440 000
images. They may not be the most relevant ones but this is a start. ;-)
I have also other ideas to improve this tiny app if it has an interest
for the community.
Displee source code (MIT) is available here:
https://github.com/Visu4link/displee
Pastec source code (LGPL) is available here:
https://github.com/Visu4link/pastec
The source code of the Displee back-end is not released yet. It is
basically a python3 Django application.
I will be glad to receive your feedback and answer any question!
Best regards,
--
Adrien Maglo
Pastec developer
http://www.pastec.io
+33 6 27 94 34 41