Wikitech-l April 2015

98 participants
78 discussions

Too many connections...
by Ilario Valdelli 10 Apr '15

10 Apr '15

Sorry, are you experiencing the same problem than me accessing to the Italian Wikipedia? Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot access the database: Too many connections (10.64.32.30)) -- Ilario Valdelli Wikimedia CH Verein zur Förderung Freien Wissens Association pour l’avancement des connaissances libre Associazione per il sostegno alla conoscenza libera Switzerland - 8008 Zürich Wikipedia: Ilario <https://meta.wikimedia.org/wiki/User:Ilario> Tel: +41764821371 http://www.wikimedia.ch

4 5

Rough Estimate of pageviews with Javascript disabled
by Nuria Ruiz 10 Apr '15

10 Apr '15

Hello! The analytics team has been working in getting a *rough *estimate on the percentage of pageviews we get for browsers with Javascript disabled. We though we should be able to provide a pretty good rough estimate using the data our hadoop cluster has as we have every single request to bits, text and mobile. The hardest part is filtering robots/spiders (from changes we hope to deploy this week this identification should be a lot easier). Our rough estimate is that *about 3% of our pageviews come from clients with **no Javacript support. *Note that some of those are browsers we do not support javascript-wise (like IE6) and others are browsers without Javascript support to speak off (Opera Mini). Details and caveats of the methodology used: *https://www.mediawiki.org/wiki/Analytics/Reports/Clients_without_JavaScript <https://www.mediawiki.org/wiki/Analytics/Reports/Clients_without_JavaScript>* Thanks, Nuria

1 0

odd namespace number
by Amir E. Aharoni 10 Apr '15

10 Apr '15

Hi, Flow has a new namespace: Topic. It has an even namespace number by default: 2600. Talk pages till now have had odd numbers, and some scripts relied on that. For example, a project to analyze usage of Hebrew online used this, um, feature to identify whether the page being analyzed is in a content namespace or a talking namespace. I'd argue that it's wrong to do it in the first place, because pages like Village Pump are in an even-numbered namespace, and their content is closer to talk pages than to content pages. Also, a program that wants to handle Flow posts will probably need APIs and queries that are different from those that are needed for handling old-style wiki pages in any case. But still, I'll ask to be on the safe side: Does anybody know how prevalent that is? Is anybody else familiar with scripts, gadgets or extensions that rely on this? (No, this is not an April fools joke. Really, it isn't. Yes, I admit that it sounds a lot like xkcd 1172. And like WP:BEANS. But no, it's not an April fools joke.) -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

6 8

Abandoned MediaWiki core branches (pre-git)
by Krinkle 10 Apr '15

10 Apr '15

Hey all, We've got a dozen or so branches that were migrated from SVN. Can we delete and/or migrate these accordingly? Nowadays these would likely live in a personal sandbox, or in a (stack of) Gerrit changes that can be iterated upon. I've made a list at mediawiki.org <http://mediawiki.org/>: https://www.mediawiki.org/wiki/User:Krinkle/Old_branches <https://www.mediawiki.org/wiki/User:Krinkle/Old_branches> API_Versioning: • Branch point: MediaWiki 1.21 • Active: December 2012 • Commits ahead: 0 (never diverged) Wikidata: • Branch point: MediaWiki 1.21 • Active: October 2012 • Users: Daniel Kinzler (brightbyte) • Commits ahead: 0 (merged into master) chinese-collation: • Branch point: MediaWiki 1.21 • Active: March 2012 - February 2013 • Commits ahead: 14 • Users: Liangent, Tim Starling iwtransclusion: • Branch point: MediaWiki 1.17 • Active: March 2012 • Commits ahead: 1 • Users: Sam Reed (reedy) make-collapsible-custom: • Branch point: MediaWiki 1.18 • Active: October 2011 • Commits ahead: 5 • Users: Liangent mobilefrontend-core-merge: • Branch point: MediaWiki 1.20 • Active: May 2012 - June 2012 • Commits ahead: 7 • Users: Arthur Richards (awjrichards) password-hashing: • Branch point: MediaWiki 1.20 • Active: March 2012 - August 2012 • Commits ahead: 22 • Users: Daniel Friesen (dantman) wikidata-wmfphase1beta: • Branch point: MediaWiki 1.21 • Active: September 2012 • Commits ahead: 0 (merged into master) • Users: Daniel Kinzler (brightbyte) — Krinkle

1 0

SMWCon Spring 2015 Final Call for Contributions
by Koerner, Chris L 09 Apr '15

09 Apr '15

=SMWCon Spring 2015 Final Call for Contributions= This is a reminder that the deadline for contributions to SMWCon is Wednesday, April 22nd. We are inviting you to submit your contributions to help collect and put together the conference program. We’ve started to rough in our schedule and would love to have a diverse group of speakers. Submit your proposed talk today! ==Call for Contributions== Talks could be about anything related to semantics, wikis, or yes semantic wikis! We welcome new contributions on the use of semantic wikis in different industries and the development and proposal of new tools in and around the semantic wiki community. You can propose your contributions on the conference website (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) in form of regular talks or short lightning talks. All submitted proposals will be reviewed and we will do our best to consider your proposal in the conference program. If you've already announced your talk it's now time to expand its description. We are also looking for folks to help us with our tutorial day. We’re looking for presentations on the basics of Semantic MediaWiki and related extensions. The deadline is April 22nd, but we encourage submissions, even in a draft form, as soon as possible to help with planning. Please note that all tutorials and presentations will be video and audio recorded and made available for others after the conference. Please add yourself to the informal list of attendees if you’d like to attend. ==Important Facts== *Submission Deadline is April 22nd (please contact the organizers if you need more time) *SMWCon is from Wednesday, May 6th to Friday, May 8th 2015 *T-Rex (http://downtowntrex.com), 911 Washington Ave., St. Louis, MO, USA *Conference site: http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015 *Participants: Everybody interested in semantic wikis, especially in Semantic MediaWiki, e.g. administrators, developers, wiki users, consultants, business representatives and researchers. ==List of Topics== Here are some suggestions. All submissions are welcome. Use of wikis in *Academia *Business *Entertainment *Research *Sciences *Social Services Use of wikis for *Knowledge Management *Community Building *Project Managmeent *Personal Wikis *Emergency Response *Event Planning Extending Semantic MediaWiki *Extensions *Integration with other services (databases, external APIs, etc) *Visualization and reporting tools Developments around Semantic MediaWiki *Community building *Feature wish lists *SMW and related extensions roadmaps *Improving the experience using semantic wikis *How to contribute to SMW and related projects *Multilingual support *Access control ==Registration== Tickets can be purchased at http://smwcons2015.eventbrite.com Your registration fee includes: *3-day Conference Pass (including the tutorial day) *Breakfast for all three days *Lunch on the first and 3rd day *Coffee, snacks *Evening social event with hors d'oeuvres and drinks Please note that the registration fee does not cover accommodation or travel expenses. ===Academic Pricing=== Attendees from education organizations can purchase a discounted ticket. Proof of affiliation may be requested. ==Organizing Committee== *Chris Koerner [Local Chair] *Paul Boal [Program Chair] ==Sponsors== *Mercy (http://mercy.net) *SNPedia (http://www.snpedia.org) This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system.

1 0

Obfuscating IP addresses on history pages
by Cristian Consonni 08 Apr '15

08 Apr '15

Hi, You may have followed the discussion on Wikimedia-l (and enwiki-l). For a mere intellectual curiosity I would like to know why hashing the IPs with a varying salt won't work. Wouldn't that provide a way to obfuscate IP addresses while maintaining uniqueness (i. e. a given IP gets alway hashed to the same hash). Tim said in a message on enwiki-l that he has looked into the matter but haven't found any satisfying solution. So what's the problem with salted hashes? Note: I have read something about hashing but I am far from being an expert, please assume I am the classical layman. Thanks in advance to anyone who will take the time to explain. C ---------- Messaggio inoltrato ---------- Da: "Lila Tretikov" <lila(a)wikimedia.org> Data: 05/Apr/2015 11:30 Oggetto: Re: [Wikimedia-l] Announcing: The Wikipedia Prize! A: "Wikimedia Mailing List" <wikimedia-l(a)lists.wikimedia.org> Cc: All, As Tim mentioned we are seriously looking at privacy/identity/security/anonymity issues, specifically as it pertains to IP address exposure -- both from legal and technical standpoint. This won't happen overnight as we need to get people to work on this and there are a lot of asks, but this is on our radar. On a related note, let's skip the sarcasm and treat each other with straightforward honestly. And for non-English speakers -- who are also (if not more) in need of this -- sarcasm can be very confusing. Thanks, Lila On Fri, Apr 3, 2015 at 4:02 PM, Cristian Consonni <kikkocristian(a)gmail.com> wrote: > Hi Brian, > > 2015-03-30 0:25 GMT+02:00 Brian <reflection(a)gmail.com>: > > Although the initial goal of the Netflix Prize was to design a > > collaborative filtering algorithm, it became notorious when the data was > > used to de-anonymize Netflix users. Researchers proved that given just a > > user's movie ratings on one site, you can plug those ratings into another > > site, such as the IMDB. You can then take that information, and with some > > Google searches and optionally a bit of cash (for websites that sell user > > information, including, in some cases, their SSN) figure out who they > are. > > You could even drive up to their house and take a selfie with them, or > > follow them to work and meet their boss and tell them about their views > on > > the topics they were editing. > > somewhat tangentially, and to bring back this to topic to a more > scientific setting I would like to point out that there has already > been reasearch in the past on this topic. > > I highly recommend reading the following paper: > > Lieberman, Michael D., and Jimmy Lin. "You Are Where You Edit: > Locating Wikipedia Contributors through Edit Histories." ICWSM. 2009. > (PDF < > http://www.pensivepuffin.com/dwmcphd/syllabi/infx598_wi12/papers/wikipedia/… > >) > > For those of you that don't want to read the whole paper, you can find > a recap of the most relevant findings in this presentation by Maurizio > Napolitano: > < > http://www.slideshare.net/napo/social-geography-wikipedia-a-quick-overwiew > > > > The main idea is associating spatial coordinates to a Wikipedia > articles when possible, this articles are called "geopages". Then you > extract from the history of articles the users which have edited a > geopage. If you plot the geopages edited by a given contributor you > can see that they tend to cluster, so you can define an "edit area". > The study finds that 30-35% of contributors concentrate their edits in > an edit area smaller than 1 deg^2 (~12,362 km^2, approximately the > area of Connecticut or Northern Ireland[1] (thanks, Wikipedia!)). > > For another free/libre project with a geographic focus like > OpenStreetMap this is even more marked, check out for example this > tool «“Your OSM Heat Map” (aka Where did you contribute?)»[2] by > Pascal Neis. > > This, of course, is not a straightforward de-anonimization but this > methods work in principle for every contributor even if you obfuscate > their IP or username (provided that you can still assign all the edits > from a given user to a unique and univocal identifier) > > C > [1] https://en.wikipedia.org/wiki/Square_degree > [2a] http://yosmhm.neis-one.org/ > [2b] http://neis-one.org/2011/08/yosmhm/ > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines > Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:[email protected]?subject=unsubscribe> > _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l(a)lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, <mailto:[email protected]?subject=unsubscribe>

4 6

MediaWiki-Vagrant directory change merged (/srv -> /vagrant/srv)
by Bryan Davis 08 Apr '15

08 Apr '15

A patch [0] was merged recently that moves files provisioned by some roles from /srv/* (and /vagrant/*) to /vagrant/srv/*. This puts the files on the host machine and reduces the number of random subdirectories under /vagrant that are created. See T89919 [1] and the patch for more details. Most users shouldn't really notice any impact from this change, but users of the iegreview, scholarships and wikimetrics roles will need to either move their /vagrant/<rolename> checkouts to /vagrant/srv/<rolename> or double check that any work in progress they have in those git clones are pushed up to gerrit and pulled back down to the new working directory. [0]: https://gerrit.wikimedia.org/r/#/c/200624/ [1]: https://phabricator.wikimedia.org/T89919 Bryan -- Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA irc: bd808 v:415.839.6885 x6855

1 0

RFC meeting this week (new time)
by Tim Starling 07 Apr '15

07 Apr '15

In the next RFC meeting we will discuss the following RFCs: * Clean up URLs <https://www.mediawiki.org/wiki/Requests_for_comment/Clean_up_URLs> * Assert <https://www.mediawiki.org/wiki/Requests_for_comment/Assert> The meeting will be on the IRC channel #wikimedia-office on chat.freenode.net at the following time: * UTC: Wednesday 21:00 * US PDT: Wednesday 14:00 * Europe CEST: Wednesday 22:00 * Australia AEST: Thursday 07:00 -- Tim Starling

1 0

REL1_25 branched
by Chad 07 Apr '15

07 Apr '15

I've just branched REL1_25 for MediaWiki core from 6dae212. Master has now been bumped to 1.26alpha. Please don't break master immediately with all kinds of backwards incompatible changes...makes backporting fixes a pain. Think of the poor release manager ;-) Also: extensions are in the process of being branched and will complete over the next hour or two. Slow script is slow. -Chad

1 0

Must the logging table be in chronological order?
by Daniel Barrett 07 Apr '15

07 Apr '15

Will anything bad happen if entries in the MediaWiki "logging" table are not inserted in chronological order? Due to a bug, our logging table has incomplete data. I'd like to insert the missing data using a script. However, the log_id column is auto-increment. This means that when the table is ordered by log_id, the data will not be in chronological order by log_timestamp. Is that bad in any way? Or are all applications (like Special:Log) expected to "order by log_timestamp" rather than log_id? Thanks, Dan

5 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2015