Just to prove that I actually do work at the Wikimedia Foundation, I’ve gone and posted a a blog post to Wikimedia’s blog.
Just to prove that I actually do work at the Wikimedia Foundation, I’ve gone and posted a a blog post to Wikimedia’s blog.
Over the last few weeks, we’ve set up a test environment on Wikimedia Labs to replicate our production cluster and test new software before it’s deployed to Wikimedia sites. This will notably allow us to identify issues with the upcoming version of MediaWiki (1.19) before its deployment — but we need your help.
In case you haven’t heard yet, Wikimedia Labs is a platform aimed to make it easier for developers and system administrators to try out improvements to Wikimedia infrastructure, including MediaWiki, and to do analytics and bot work.
In the past, we’ve used prototype wikis to set up testing environments for upcoming releases of MediaWiki or to test new features. This has been helpful, but has suffered from lack of ongoing maintenance.
Over the holidays, I had the idea — with the upcoming 1.19 release, and the Labs servers newly online and available for non-WMF staff — of using Wikimedia Labs to duplicate the production cluster’s configuration in the Labs environment, and work with volunteers to help maintain this environment.
I particularly want to thank the following people for their work on this project:
We’ve recently opened this up for the real testing, so now is the time to jump in. Please look at the cluster’s SiteMatrix and find wikis to test. Try reading, editing, using your favorite gadgets, and so on as you normally would; treat it as a giant sandbox. If you find a problem, please report it on the problem reports page.
With your help, we can make the upcoming upgrade smoother.
Mark A. Hershberger, Bugmeister
In a previous blog post, we discussed our readers’ perception of article quality. In addition, we asked our readers to compare Wikipedia as a whole to other prominent websites – Facebook, Twitter, New York Times, Google, YouTube, Yahoo and CNN. Of course, there are several key differences between them, but we wanted to understand how Wikipedia stacks up against other high-traffic websites.
Readers from all 16 countries in our sample compared Wikipedia’s interface and ease of navigation to other Internet properties. If we look at the sample as whole, Wikipedia (8.09 on 10) was rated a close second to Google (8.44) on these measures. What makes this even more interesting is Wikipedia’s relationship with the search engine, which we mention in an earlier blog post. Although ratings varied across countries quite significantly, in most cases there was little deviation in ratings relative to other websites, with some exceptions.
When asked about the Wikipedia interface, readers scored Wikipedia 7.92 out of 10 on average, just behind Google (8.3). About 46 percent of our readers scored the interface 9+ out of 10, compared to 54 percent for Google. We did not find significant deviations across countries or languages, with one exception: Readers in Egypt (and by extension, Arabic speakers) rated Wikipedia lower than YouTube, Facebook and Yahoo. A desire for better right-to-left support is one plausible explanation for the result.
Readers scored Wikipedia 8.27 on this metric, slightly lower than Google (8.59). 53 percent of our readers rated the ease of navigation 9+ out of 10, compared to 63 percent for Google. As above, Arabic/Egyptian readers rated Wikipedia below YouTube, Facebook, and Yahoo.
Mani Pande, Head of Global Development Research
Ayush Khanna, Data Analyst, Global Development
We recently conducted an online survey of Wikipedia readers, limited to 250 participants each in 16 countries. This is the seventh in a series of blog posts summarizing our findings. If you are interested, you can find out more about the methodology of the survey here.
Después de la versión en inglés, abajo, versión en español
Sometimes innovation is the result of being in the right place at the right time as well as being flexible. I am an English as a foreign language teacher in central Mexico and a long time learner of Spanish. Needing intensive Spanish reading practice, I discovered the benefits of writing Wikipedia articles about Mexico (researching in Spanish, writing in English) to both myself and to the encyclopedia. Wanting to share this experience with my students, in Fall 2007, I designed and taught a Wikipedia based class for ITESM-Campus Toluca’s most advanced English students as an experiment with support of my department.

ITESM students participate in an edit-a-thon in cooperation with the Children's Museum of Indianapolis.
As these students were already well versed in vocabulary and grammar, real world practice or “authentic communication” was more important. As most language learners know, the best way to learn a language is to be immersed in a situation where its use is necessary. Computer technology, especially the virtual world of the Internet, has created a number of virtual “worlds” and social groups, not the least of which is the Wikipedia community. The goal in the Fall 2007 class was to introduce this virtual world of English language Wikipedia and explore ways to participate, culminating in the writing of a complete article from scratch as a final project. Mind you, this was before the advent of many of the programs the Wikimedia Foundation has today, such as the Wikipedia Global Education Program.
The class revolved around intercultural communication – learning about potential differences and strategies for coping. For this aspect of the course, the Wikipedia community was introduced as a culture, a group of people with a shared set of values and means by which they interrelate… something the students would have to adapt to as they learned how to write articles and deal with wiki mark up. As it was very different from any other English class they had ever experienced, almost all the students struggled in some way in the course. However, most improved their English language skills, based on TOEFL test scores taken before and after the semester. These findings were presented to the MexTESOL 2008 conference in León, Guanajuato, Mexico.
In 2008, I transferred to the Ciudad de México (Mexico City) or CCM campus of the same school system to establish and run their self access language learning laboratory (think of a hybrid of a traditional language lab and library). Since that time, I have done smaller Wikipedia-based assignments with students, writing smaller articles in groups and moving to translation exercises – mostly English language Wikipedia articles into Spanish. Translation has proven to be a good introduction to Wikipedia editing for many students. It is one way students can improve Wikipedia in their native language. It is easier to translate from one’s non native language into one’s native language, but it has been noted that the English of the original article still causes transference errors into the Spanish version. This problem has been dealt with through peer review – students doing translation in groups, checking each other’s work and then groups exchanging translated articles for final review. This often leads to interesting discussions about how English and Spanish differ rhetorically, that is, how each writing style prefers to express information. This, too, is part of intercultural communication.
So far, there have been two major lessons learned from the use of Wikipedia. First, the demands of acculturating oneself into the Wikipedia community is a good experience in that many students experience the real frustrations and symptoms of culture shock. But this benefit is not for everyone. It is by far best for students who see the value in the experience, despite whatever frustrations might occur. In the Fall of 2011, I worked with four such students, who led on projects such as creating articles on Mexico’s Festival Internacional Cervantino. Not only did these students research and write articles in both Spanish and English, they also contacted Festival organizers and various international artists to obtain photographs and other assistance. Second, the use of translation assignments is also extremely useful. It provides a template of how Wikipedia articles are generally set up and is a good introduction to technical aspects of contributing to Wikipedia. It allows for learning through imitation, rather than learning abstract rules then guessing how to apply them. It also provides a way to work with Wikipedia which is less intense and easier to incorporate into classes, especially language classes.
ITESM-Campus Ciudad de México continues to be committed to developing working with Wikipedia. The campus library director, Lourdes Epstein has dedicated space in the facility for Club Wikipedia and students working on Wikipedia related assignments. Several departments, including Global Studies, promote involvement with Wikipedia to their students and faculty. For the Spring 2012, a pilot program with the campus’s high school level International Baccalaureate program begins. A select group of students will set up semester-long projects based on their interests and abilities mentored by myself as part of their CAS or social service requirement.
A veces la innovación es el resultado tanto de encontrarse en el lugar indicado, en el momento indicado, como de ser una persona flexible. Yo enseño inglés en México y hace mucho tiempo que estudio y hablo español. Viéndome en la necesidad de practicar lectura en español de manera intensiva, descubrí los beneficios (tanto para mí como para la enciclopedia) de redactar artículos de Wikipedia sobre México (investigando en español y redactándolos en inglés). Con el deseo de compartir esta experiencia con mis alumnos, en la segunda mitad de 2007, diseñé e impartí, en el Campus Toluca del ITESM, un curso basado en Wikipedia, para los alumnos de inglés más avanzados, con el apoyo del departamento para el que trabajaba.
Como esos alumnos ya habían estudiado vocabulario y gramática en varios cursos, lo más importante, en términos de aprendizaje, consistía en la práctica de situaciones conversacionales auténticas. Como la mayoría de los estudiantes sabe, la mejor manera de aprender una lengua es la inmersión en una situación donde hablar sea imprescindible. La tecnología informática, sobre todo el mundo virtual de la Internet, ha creado muchos “mundos virtuales” y grupos sociales. La comunidad de colaboradores de Wikipedia es una de las más importantes. La meta de aquel curso de 2007 era doble: presentar el mundo virtual de Wikipedia en inglés y explorar las formas de colaboración con ese mundo; y esa meta se conseguía redactando de cero un artículo, como proyecto final. Hay que recordar que esto ocurrió antes del inicio de muchos de los programas actuales de la Fundación Wikimedia, tales como el Global Education.
El curso se centraba en la comunicación intercultural – aprender sobre las diferencias potenciales entre ambas culturas y las posibles estrategias de adaptación. Para cumplir con ese objetivo, se presentó a Wikipedia como una “cultura”; es decir, como a un grupo con valores compartidos y maneras de interactuar…algo que los alumnos debían adoptar mientras aprendían a redactar artículos y se familiarizaban con los aspectos tecnológicos del sitio. Dado que la propuesta difería mucho de cualquier otra clase de inglés que hubieran cursado previamente, casi todos los alumnos experimentaron distintos tipos de dificultades durante el semestre. Sin embargo, la mayoría mejoró su desempeño lingüístico en inglés, como lo mostraron los resultados del examen TOEFL (realizado antes y después del curso). Presenté toda la información recogida entonces en la conferencia de MexTESOL, realizada en León, Estado de Guanajuato (Estados Unidos Mexicanos), en 2008.
En 2008, comencé a trabajar en el Campus Ciudad de México con el fin de establecer y coordinar el laboratorio de aprendizaje autodirigido (self access), que es una mezcla de laboratorio de idiomas tradicional y biblioteca. Desde entonces, junto con mis alumnos, realizo tareas menores para Wikipedia, como redactar en grupos artículos más breves y encomendar la traducción de artículos, principalmente del inglés al español. A muchos estudiantes, la traducción les resultó una buena introducción a la preparación de artículos de Wikipedia. Es una manera de que ellos mejoren Wikipedia en su lengua materna. Es más fácil traducir de otra lengua a la propia, aunque todavía se nota que el inglés de los originales causa errores de transferencia en la versión española. Esta cuestión se resolvió mediante la revisión de las distintas versiones entre los mismos traductores. La traducción se realiza en grupos, revisando cada uno de los traductores los borradores de sus compañeros, y después se intercambian los artículos completos en vistas de una revisión final. Frecuentemente, esto lleva a debates interesantes acerca de las diferencias retóricas entre el inglés y el español; o sea, acerca de cómo, en cada lengua, las figuras retóricas expresan la misma información. Esto, también, forma parte de la comunicación cultural.
Hasta la fecha, se obtuvieron dos lecciones importantes gracias al uso de Wikipedia. Primero, las exigencias de aculturación de cada participante a la comunidad de Wikipedia es una experiencia valiosa, porque así muchos alumnos pueden experimentar las dificultades y los síntomas reales del choque cultural. Sin embargo, no todos se benefician de esto; los que más provecho sacan son los alumnos que perciben el valor de la experiencia a pesar de los obstáculos. En la segunda mitad de 2011, trabajé con cuatro de estos alumnos, que se abocaron a la redacción de los artículos relativos al Festival Internacional Cervantino. Estos estudiantes no solo investigaron y redactaron los artículos en inglés y español, sino que también se comunicaron con los organizadores del festival y con varios artistas internacionales para obtener fotografías y otros tipos de ayuda. En segundo lugar, las tareas de traducción son extremadamente útiles porque proveen un molde para el formato de los artículos de Wikipedia y son buenas también para introducir los aspectos técnicos de Wikipedia. Traducir permite aprender por imitación en lugar de primero aprender reglas abstractas y luego intentar aplicarlas de alguna manera. También muestra un modo de trabajar con Wikipedia que es menos intenso y más fácil de incorporar en las clases, sobretodo en clases de lenguas extranjeras.
El Campus Ciudad de México no ha cejado en su compromiso de colaborar con Wikipedia. Lourdes Epstein, Directora de la Biblioteca del campus, apartó un espacio especial, en el mismo edificio de la biblioteca, para el Club Wikipedia y para otros alumnos que colaboren en tareas afines. Varios departamentos universitarios, como el de Estudios Globales, promueven la participación de sus alumnos y docentes. En el primer semestre del corriente año, dará comienzo un programa piloto en el que participarán los alumnos del Programa del Diploma del Bachillerato Internacional del campus. A fin de cumplir con el requisito de servicio social “CAS”, un grupo seleccionado de alumnos va a idear proyectos, asesorados por mí, de un semestre de duración, basados en sus intereses y habilidades.
Please find below the summary part of the mid-year status report from the Wikimedia Foundation’s Global Development department, regarding the 2011-12 annual plan. The full report including the core activity review and priorities for next six months can be accessed on Meta.
Overall, the global development team continues to make progress in building our team, however we are moving more slowly than would be preferred in some areas. I’m happy that we have made a huge amount of progress in Mobile over the past six months. I would like to be further along in deploying pilot programs in India and Brazil as well as in expanding our grants program. The slower than desired pace is a result of our desire to do a better job of working with the communities where we are deeply engaged, a desire to do more upfront consultation and design work, and due to our relatively thinly spread leadership resource (me). We are also actively reflecting on the Pune Pilot and integrating lessons into how we work across the board, not just in the Global Education Project or in India.
We are on track to meet our plan for our mobile target of 2 billion page views for 2011/12 and partnerships with mobile operators representing 500 million subscribers. In December 2011, we had 1.534 billion page views to our mobile sites across all Wikipedias as compared with 802 million in June 2011.[1] We have made excellent progress across the organization on mobile over the past six months and are in a fundamentally better place than we were. Our mobile partnerships team has built a pipeline of partnerships with mobile operators around the world that start launching in January. Our current partnership list covers key markets in Latin America, Asia, Middle East and Africa, Turkey and Russia representing over 700 million subscribers. Not every deal will come to fruition, but we are confident that some major ones will and we’ll begin to attract wider interest in partnerships. In most cases, our partners will be offering Wikipedia access for free to their subscribers and we are working on marketing programs that will expand reach.
The Global Development team works closely with engineering on mobile research, product feature decision making and on technical support for partners. Our engineering team has deployed a much-improved mobile gateway and enhanced its functionality, and is working hard to release an Android app, which closes a hole in our portfolio. They are building out our engineering resources to enable continuous improvement of our mobile position. GD/Eng’s mobile research work (we have done two major studies) has helped inform engineering decisions on the product development pathway. Results from the Mobile Readers Survey 2011 are being analyzed, and will be shared soon. Findings from the mobile research work conducted in India and Brazil can be found at Wikipedia Mobile User Research.
Progress on editor growth has been more challenging. We are behind in getting pilot initiatives deployed to really understand the potential for direct impact on editor growth. Our primary effort to date has been the Global Education Program including the Pune Pilot in India. While the program in the US and Canada continues to grow, it has had a small and temporary impact on editor numbers. The program has not been oriented toward creating new Wikipedians, but has added almost 2,000 editors during the Fall 2011 semester, more than thrice the number from Spring 2011 (500+).
The Pune Pilot, which we launched in June, has wrapped up, but was a failure. There were a range of problems involving student plagiarism and the program took on too many students with too few support resources to manage the problems that came up. We also taxed the English Wikipedia community in a way that we had not intended and was regrettable. We learned a lot…and are engaged in a thorough review of the pilot with outside help to ensure we capture the lessons and make better and different mistakes in the future.
We did not have the capacity in place to launch other pilot initiatives in the past six months. We slowed down our plans for Brazil to create space to build a strong relationship with the Brazilian community and conduct some research into the current state of PT:WP. Our India program was at full capacity dealing with the Pune Pilot, supporting the Wikiconference India, and basic program setup requirements. Our India team also took some time to strengthen their links to the community and do a better job of getting early community partnership in program work.
An unplanned for opportunity emerged to accelerate catalyst activities in MENA focused on Arabic Wikipedia. It was not in the annual plan to work in MENA this year, but we took the opportunity presented by the interest of the Qatar Computing Research Institute in supporting Wikipedia. They hosted a small workshop where we met with leading Arabic Wikipedians and laid the groundwork for program work in the beginning of 2012.
see full report
see full report
Chief Global Development Officer
Two weeks ago, we submitted the official Wikipedia Android App into Google’s Android Market. Since then, we’ve seen an amazing reaction from our Android users. We’ve had over 500,000 installs, we’ve become #4 in top free books and reference, and we held the #1 trending spot in the whole Android Market last week. Those stats don’t even reflect how great we’ve been doing internationally. Thank you to our users for supporting us.
We wanted to do this blog post sooner, but we had a busy news week helping to protect the Internet and releasing two important updates to fix GPS and performance related issues. Now, we’re excited to talk about it.
Our Android app marks a really important turning point for the Wikimedia mobile projects and the open web in general. Instead of developing a native application as we had done previously with our iOS Wikipedia app, we opted to simplify our development efforts by using PhoneGap. Fully embracing HTML5, CSS3, & Javascript commits us to the open Web technologies of the future. Rather than diving into proprietary frameworks and SDKs, our application has been built on the same foundation as the open mobile web. And not only does this allow us to prepare for the future, it also accelerates our ability to develop across numerous platforms.
Within a short amount of time we’ve already developed a testing version of our iOS app with PhoneGap and we’ve established our first complete community port to the BlackBerry PlayBook. This demonstrates the power of using open tools and communities to improve the Internet as a whole and it is a critical component to our long term goals.
But there is a lot more to do. We’ve received excellent feedback from our reviewers and we’ve started to incorporate it into our roadmap. Future versions of all of our apps will include a lot of what we’ve heard from our users, but we need help to get there. Our code is all open source and its easy to get involved. Fork our code, reach millions, and help educate the world.
Given Android’s significant smartphone market share, having an Official App may be a “must” these days, but there are additional reasons that this release is important for us. First, the app is truly international. Unlike our iOS app, which was only localized into four languages, our Android app already has complete localization for 25 languages, nearly-complete localization for over 50 languages, and it can be translated to over 250 languages languages through translatewiki.
As importantly, it opens up new distribution opportunities for people to discover Wikipedia. As we develop mobile partnerships throughout the Global South, (see our recent announcement with Orange), we hope to distribute this app through operators’ local app stores in addition to Android Market. This not only broadens Wikipedia’s reach, it also gives our operator partners a free, unique, and locally relevant offering for their customers, strengthening the overall impact of these partnerships.
Finally, the rise in low-cost Android smartphones is making the web more broadly accessible to people who may not have had Internet access previously. This is in alignment with our mobile mission to reduce barriers to accessing free knowledge.
We’re excited to celebrate this release, both as a development milestone and a mission-aligned achievement. And we are thrilled to get the app into the hands of more people around the world. Now, let’s make some noise.
Tomasz Finc, Director of Mobile and Special Projects
Amit Kapoor, Senior Manager, Mobile Partnerships
Jump to the code if you’re not interested in the backstory.
I recently had to investigate how to customize the “meta” widget provided by WordPress.
I maintain the Wikimedia Blog, and we wanted to include a link to our posting guidelines to the “meta” section of our sidebar.
There is no straightforward way to do this; the widget can’t be edited from within the admin area.
One possibility was to replace the standard meta widget by a custom text widget, with the same content and links, and to add our guidelines to the mix. But this meant losing the nice context-aware links (e.g. “Register” vs. “Site admin”, and “Log in” vs. “Log out”, respectively for logged-out and logged-in users) provided by built-in WordPress functions (wp_register and wp_loginout): widget text can’t embed PHP code.
Another possibility was to install a third-party plugin to customize the meta widget (or allow PHP code in widget text). I’m usually reluctant to using plugins for simple changes like the one we wanted to do. Both our Operations staff and I prefer to keep the amount of third-party plugins installed on the blog to a minimum, for various reasons (security, maintenance, maintainability, etc.)
Because there are no hooks to plug into the widget’s behavior, most of the solutions I’ve seen online consist either of using a third-party plugin, or messing with WordPress core files, which is a no-go for me.
The third possibility, which is the one I went for, was to create our own meta widget. This is what the code below does.
I used the WordPress widgets API to create a widget, as well as the content of the standard meta widget, located in wp-includes/default-widgets.php. The code is located in our WMBlog plugin, a set of customizations specific to our blog that work independently of the theme.
The custom widget replicates the functionality of the standard meta widget (with the handy context-aware links) and also includes the link to our guidelines. It was a bit more work, but it’s cleaner and more robust that way. Once the widget is available, an admin can replace the standard widget with the custom one.
If you want to add stuff to the meta widget, or remove some of its standard content, this is probably the Right™ Way to do it. You’ll want to look at lines 42 to 51 in the code below.
Note: The code hasn’t been deployed to production yet; it’ll appear on the Wikimedia blog in a few days.
/* =========================================================
Replicate the default meta widget and extend it to include
a link to the Wikimedia blog guidelines */
class WMBlog_meta_widget extends WP_Widget {
function WMBlog_meta_widget() {
// (constructor) Instantiate the parent object
parent::WP_Widget( /* Base ID */'WMBlog_meta_widget', /* Name */'WMBlog_meta_widget', array( 'description' => 'The default meta widget plus Wikimedia-specific stuff' ) );
}
function form( $instance ) {
// output the options form on admin
// i.e. for now only the widget's title
if ( $instance ) {
$title = esc_attr( $instance[ 'title' ] );
}
else {
$title = __( 'New title', 'text_domain' );
}
?>
<p>
<label for="<?php echo $this->get_field_id('title'); ?>"><?php _e('Title:'); ?></label>
<input class="widefat" id="<?php echo $this->get_field_id('title'); ?>" name="<?php echo $this->get_field_name('title'); ?>" type="text" value="<?php echo $title; ?>" />
</p>
<?php
}
function update( $new_instance, $old_instance ) {
// process widget options to be saved
$instance = $old_instance;
$instance['title'] = strip_tags($new_instance['title']);
return $instance;
}
function widget( $args, $instance ) {
// output the content of the widget
extract( $args );
$title = apply_filters( 'widget_title', $instance['title'] );
echo $before_widget;
if ( !empty( $title ) ) { echo $before_title . $title . $after_title; } ?>
<ul>
<?php wp_register(); ?>
<li><?php wp_loginout(); ?></li>
// Link to our own posting guidelines
<li><a href="//meta.wikimedia.org/wiki/Wikimedia_Blog/Guidelines" title="General contribution guidelines for the Wikimedia blog">Blog guidelines</a></li>
<li><a href="<?php bloginfo('rss2_url'); ?>" title="<?php echo esc_attr(__('Syndicate this site using RSS 2.0')); ?>"><?php _e('Entries <abbr title="Really Simple Syndication">RSS</abbr>'); ?></a></li>
<li><a href="<?php bloginfo('comments_rss2_url'); ?>" title="<?php echo esc_attr(__('The latest comments to all posts in RSS')); ?>"><?php _e('Comments <abbr title="Really Simple Syndication">RSS</abbr>'); ?></a></li>
<li><a href="http://wordpress.org/" title="<?php echo esc_attr(__('Powered by WordPress, state-of-the-art semantic personal publishing platform.')); ?>">WordPress.org</a></li>
<?php wp_meta(); ?>
</ul>
<?php echo $after_widget;
}
}
function WMBlog_register_widgets() {
// register the plugin's available widgets
register_widget( 'WMBlog_meta_widget' );
}
// plug in the widgets registration
add_action( 'widgets_init', 'WMBlog_register_widgets' );
Yesterday, we deployed a new MediaWiki extension, FeaturedFeeds, to all Wikimedia wikis. It creates syndication feeds (Atom or RSS) of Wikipedia’s featured content, such as featured articles or pictures of the day, giving the projects a new way to deliver content to readers and users.
For now, links to the feeds only appear in page metadata; in the future, we will add them to the sidebar on main pages, if communities wish so.
FeaturedFeeds integrates with the existing main page infrastructure: it uses data from templates to show content based on the current date.
Because user-generated content is involved, local wiki administrators need to make a few edits to MediaWiki pages to set up the extension. Instructions and a FAQ will guide you through the process. You can also use my edits to set up FeaturedFeeds on the English Wikipedia as an example.
If you have questions, you can ask for help on IRC, in #mediawiki and #wikimedia-mobile; we’ll be happy to help you set up the extension on your wiki.
Max Semenik
Mobile team developer
News and notes: SOPA blackout, Orange
In the news: World watched as Wikipedia shut down for SOPA blackout
WikiProject report: The Golden Horseshoe: WikiProject Toronto
Featured content: Interview with Muhammad Mahdi Karim and the best of the week
Arbitration report: Four open cases, proposed decision in Muhammad images, AUSC call for applications
Technology report: Looking ahead to MediaWiki 1.19 and related issues
While we devised a specific set of metrics to guide our choices – including impact, innovation, transparency, accountability and efficiency – there is no science in the measuring. How does one – after all – compare the fundamental societal impact of an organization like the Wikimedia Foundation, with the tangible outputs of a well oiled humanitarian machine?Nevertheless, there is clearly love in their thumbnail sketches of the 100 organizations they profile, and I am proud to see Wikimedia's work recognized and used as general global inspiration.
Ultimately, we hope this list will inform, stimulate debate, inspire and – most of all – shine a light on the incredible dedication that continues to be displayed in and out of the spotlight on a daily basis.
Here are a few plots and data I collected for the SOPA blackout from 18 January. Wikimedia Foundation is working on a wider coverage of the event.
Note that on the second day hourly hits to Special:CongressLookup page exceeded hits to SOPA_initiative/Learn_More. Probably part of the demand came from external referrers.
The huge dip in CongressLookup hits on the first day was during hours where most US citizens were asleep. Of course the CongressLookup page did not make much sense for non-US citizens.
Here is a list of most visited SOPA related pages on different Wikipedias during the blackout (24 hrs only).
Overall page requests to English Wikipedia during the blackout was not particularly high or low.

On Saturday 28 January 2012 at 20:00 UTC there will be a workshop on Translation tools. It will take between 60 and 90 minutes and will consist of an introduction of use cases and features, as well as a Q&A. (local times)
The workshop will focus on the use cases covered by the Translate extension on Wikimedia Meta-Wiki for the following user roles:
Please put the following page on your watchlist and write your name down if you would like to attend. The workshop is held online using WebEx. I would advise you to log in 15 minutes in advance to ensure you have ample time to set up your computer if you have not used WebEx before. WebEx can be used in desktop environments on Linux, OSX and Windows.
If you would like to familiarise yourself with the technology before the workshop, please take a look at the elaborate documentation, which includes some tutorials. In the next two weeks, the already present documentation for translators will also be completed.
Credit goes to Pete Forsyth for proposing to have this workshop. Hope to see you online Saturday!
Siebrand Mazeland
Product Manager Localisation
Wikimedia Foundation
by GerardM (noreply@blogger.com) at January 24, 2012 09:56 PM
The Wikimedia Foundation is working to make knowledge freely available to every person in the world, but for many potential readers in developing countries, the only way to access the Internet is by paying for data on a mobile phone. Cost is a barrier that prevents data usage and makes access to a vast repository of knowledge like Wikipedia impossible. In some developing countries, the poorest fifth of the population already spends over 20 percent of their income on mobile phone services [1]. We don’t want people sacrificing their basic human needs to spend money on data, so we decided to do something about it.
Today we are proud to announce [2] a significant step in breaking down barriers to free knowledge: the Wikimedia Foundation and Orange are partnering to offer access to Wikipedia for Orange mobile customers free of charge. Orange has committed to provide this service in twenty countries across Africa and the Middle East, for three years, and has included access to all of Wikipedia’s enormous store of images. We have worked with Orange over the last few years and they have really come to understand the value of our mission. Thanks to their leadership, we will reach tens of millions of people that wouldn’t otherwise have access to Wikipedia — and all for free.
Over the past year, we’ve been urging mobile operators around the world to consider waiving data charges to access Wikipedia, even when we didn’t have the internal capacity to support such an endeavor. Despite not having a full-time mobile developer on staff until eight months ago, we operated in the mode of “if we build it, they will come.” I’ve focused our mobile team to help in developing countries, as we’ve fostered negotiations with operator partners. And over the last six months we’ve grown our mobile team to six people, with additional contractors (and more hires on the way). Many people on our mobile team have been critical to making this happen including Amit Kapoor, Patrick Reilly, Phil Chang and Tomasz Finc, with special help from tech ops including CT Woo and Asher Feldman – and dozens of volunteers from around the world.
The Orange rollout will begin over the next several months, starting in Tunisia and the Ivory Coast, with four to six more countries including Mauritius and Cameroon and others shortly after. The first countries will require a lot of testing and if you’re an Orange customer in one of the regions where the rollouts are happening, we’d love your comments. You can read more about this partnership via our Q&A [3]. We’ll keep you updated on our progress in future blog posts.
Orange has helped us get one step closer to making it possible to give everyone free access to the sum of all knowledge. We sincerely thank them for that. This is a really important precedent. Now we need more operators around the world to join in offering Wikipedia to their customers free of data charges. The movement for free mobile for Wikipedia has just begun.
Kul Takanao Wadhwa
Head of Mobile
Consolidation was the name of the game for the past sprint for Wikimedia’s Localisation team. A bug triage, testing, documentation and bug fixes were the activities designed to make our software more stable and more usable. When you read the bug triage report it becomes clear how much the devil is in the details; real native language expertise is needed to understand and assess the issues we aim to solve. Read the report and you will see how much we rely on our community, on people like Srikanth and Nemo_bis.
Now that we are writing documentation in a central place, like here on the language statistics of the Translate extension, we are now able to provide you with a help text that is specific to the context. For the language statistics it is a help text about “statistics and reporting“. This functionality is ready but will become available in the deployment of January 30. You can help us and yourself by reading and understanding the text. Ask when you have questions and you can translate the text and make the text that much more your own.
Narayam is another extension that has been improved with user documentation. This documentation is completely new and it can effectively replace existing documentation. The existing documentation has the benefit of being written in the local language and we expect that what is written will be similar to the Narayam documentation. It is therefore that it will be the choice of the language communities to decide if they want to point to the local documentation. Like all our software, the Narayam documentation will be available for translation. Having the translation ready may be one of the considerations.
A lot of work is going into the description of the many input methods like the Inscipt layout for Assamese. These descriptions are “must have” help information when you do not know a particular keyboard layout by heart. They also provide a wonderful opportunity to verify if our implementation for a particular keyboard method is correct. This is yet another instance where native speakers can help us a lot.
Testing and getting to grips with the different tools was a major goal for this sprint. PHPunit and Qunit is what is used to test PHP and JavaScript and the tests developed are used in an environment called TestSwarm and Jenkins (respectively for PHP and JavaScript). As our team is so much into language support, we are learning what the limits are for testing for different languages and scripts.
All in all there may have been a slush and we have done a lot of code review, but we also managed to make sure that our functionality has gained stability for this and future releases. Additionally, work was done on grammar support for JavaScript, but the patch for that was stuffed in a bug report because of the slush, as the story was moved to the next sprint. Grammar support is what fills the gap in localisation support between JavaScript and PHP and makes it available to any and all other developers.
Thanks,
Gerard Meijssen
Internationalization / Localization outreach consultant
The MIT Press I contributed to with a chapter is out! It is titled “The Reputation Society: how online opinions are reshaping the offline world” and edited by Hassan Masum and Mark Tovey.
It is available on MIT press and on Amazon.
The chapter I wrote is titled Trust It Forward: Tyranny of the Majority or Echo Chambers? and on it I ramble about objectivity/subjectivity, minorities/majorities, etc.
If reputation systems weight all perspectives similarly, they may devolve into simple majority rule. But if they give each user reputation scores that take only other similar users’ opinions into account, they run the risk of becoming “echo chambers” in which like-minded people reinforce each others’ views without being open to outside perspectives. Massa discusses design choices and trust metrics that may help balance these two extremes and the broader implication for our future societies.
The book received endorsements by people I really admire.
“As our societies expand from local villages to global networks, our ways of assessing and sharing reputation—the foundation of trust and community—must also evolve, but how? The thoughtful and thought-provoking essays in The Reputation Society bring a wide range of perspectives to this question, including the design of technological solutions, applications in philanthropy, science and governance, and warnings about the loss of privacy and autonomy. It is a fascinating collection of readings not only for scholars, but for anyone interested in the dynamics of the reviews and recommendations that shape our decisions—or in the future of how we will judge and be judged.”
—Judith Donath, Fellow, Berkman Center for Internet and Society, Harvard University
“Today is tomorrow’s yesterday. These provocative essays, by some of the leading thinkers in the domain of reputation systems, illuminate how reputations regulate actions across time and social distance and point to the opportunities and obstacles that reputation systems present for commerce and democracy.”
—Paul Resnick, Professor, University of Michigan School of Information
“The Reputation Society enriches the discussion of reputation by bringing together technologists, philosophers, legal scholars, and industry leaders to sort through the promise and perils we face today. It covers the practical, for those interested in the nuts and bolts of the challenges we face today, and the theoretical, for those looking to engage in broader discussions of the ethical and moral concerns. In short, a terrific and enlightening read!”
—Danielle Keats Citron, Professor of Law, University of Maryland School of Law
The list of my co-authors is also very delightful.
Trust, reputation systems, and the immune system of democracy / Craig Newmark –
Building the reputation society / Hassan Masum, Mark Tovey, & Yi-Cheng Zhang –
Designing reputation systems for the social web / Chrysanthos Dellarocas –
Web reputation systems and the real world / Randy Farmer –
An inquiry into effective reputation and rating systems / John Henry Clippinger –
The biology of reputation / John Whitfield –
Regulating reputation / Eric Goldman –
Less regulation, more reputation / Lior Strahilevitz –
The role of reputation systems in managing online communities / Cliff Lampe –
Attention philanthropy : giving reputation a boost / Alex Steffen –
Making use of reputation systems in philanthropy / Marc Maxson & Mari Kuraishi –
The measurement and mismeasurement of science / Michael Nielsen –
Usage-based reputation metrics in science / Victor Henning, Jason Hoyt, and Jan Reichelt –
Open access and academic reputation / John Willinsky –
Reputation-based governance and making states “legible” to their citizens / Lucio Picci –
Trust it forward : tyranny of the majority or echo chambers? / Paolo Massa –
Rating in large-scale argumentation systems / Luca Iandoli, Josh Introne, & Mark Klein –
Privacy, context, and oversharing : reputational challenges in a Web 2.0 world / Michael Zimmer & Anthony Hoffman –
The future of reputation networks / Jamais Cascio –
“I hope you know this is going on your permanent record” / Madeline Ashby & Cory Doctorow.
The cover of the book reads as follows.
In making decisions, we often seek advice. Online, we check Amazon recommendations, eBay vendors’ histories, TripAdvisor ratings, and even our elected representatives’ voting records. These online reputation systems serve as filters for information overload. In this book, experts discuss the benefits and risks of such online tools.
The contributors offer expert perspectives that range from philanthropy and open access to science and law, addressing reputation systems in theory and practice. Properly designed reputation systems, they argue, have the potential to create a “reputation society,” reshaping society for the better by promoting accountability through the mediated judgments of billions of people. Effective design can also steer systems away from the pitfalls of online opinion sharing by motivating truth-telling, protecting personal privacy, and discouraging digital vigilantism.
I’ve been interviewed by the Italian newspaper Corriere della Sera about Manypedia (and Wikitrip). If you know Italian, you can read the resulting article titled “Every Wikipedia represents its own culture: even the concept of controversiality is controversial” at corriere.it. The journalist liked to stress the fact both Manypedia and WikiTrip are open source, which is a good thing I think.

Today the Global Journal, a Geneva-based publication focusing on issues facing global businesses, NGOs, and public sector workers announced that the Wikimedia Foundation was at the very top of their list of the 100 best NGOs.
The Journal pointed out that the Foundation is “changing the world with an idea: to create a public space where all people can freely join to collaborate, share and communicate all of our collective knowledge.” The Journal also recognized WMF’s collaborative roots and our movement’s belief that information is a non-profit commodity. Among other global NGOs nominated in the list: Oxfam, International Rescue Committee, Creative Commons, and Habitat for Humanity.
Our thanks to the Global Journal for recognizing the Foundation, but especially for recognizing the work of our 100,000-strong global, volunteer community.
Jay Walsh, Communications
by GerardM (noreply@blogger.com) at January 22, 2012 04:02 PM
Teylers Museum, the 'Gehoorzaal'
Wikimedia Nederland had its 2012 new year’s reception at the Teylers Museum in Haarlem. It calls itself the first and oldest museum of the Netherlands. Ca. 150 Wikimedians and Wikipedia fans came together and saw an amazing collection, including some of the rooms closed to the ‘ordinary’ audience.
In her welcoming speech Marjan Scharloo, general director, mentioned the political and philosophical implications of Teylers Museum’s mission in the 18th century: spreading knowledge to the people. As president of WMNL, I looked back at our activities of 2011 and presented some of 2012. Maarten Dammers explained about a ‘Challenge’ competition that will have prize winners in May.
A great beginning of the new year, with a lot of new people interested in a membership of WMNL.
Yesterday I went to an open discussion about SOPA with Jason Altmire, who represents my district. He came out against SOPA at the end of the event. But one thing that bugged me was that just about everyone used “theft” as a synonym for copyright infringement. And this “theft” by rogue websites in China and southeast Asia, everyone supposedly agrees, is a serious problem, even if SOPA isn’t the right answer.
Consider a typical case where somebody downloads a Hollywood movie to watch, without paying for it. Taking this movie wasn’t authorized by the copyright holders. But the copyright holders still own it. They still have all their copies, and they are still free to make more. They can distribute and license it as they wish. They can make sequels and spin-offs and t-shirts and bobble-heads.
What would you call that? I would call it copyright infringement, but I wouldn’t call it theft.
Now imagine a different scenario. A work you have is taken from you. And once it’s been taken, you can no longer make copies. In fact, you have to get rid of all the copies you have. When it was yours, you could make copies, send them to your friends, make derivitives, use it as a jumping off point for new works. You could do with it as you pleased. Now, you can’t do any of that without the permission of the person who took it from you.
Would you call that theft?
I would call it Golan v. Holder. Wikimedians are having to get rid of thousands of public domain works from Wikipedia and Wikimedia Commons that used to be public domain in the U.S.—used to belong to the public, to use and copy and build from—which were put back into copyright by Congress. And the Supreme Court just decided that in fact, that’s just fine.
Related posts:
Wikipedia is a place where you must learn to think for yourself, encyclopedias are places where you are told what to believe.
Of course, there is a lot to like about the arbitrary exercise of authority if you have faith in the authority in question: the gullible are not duped, the conspiracy theorists are silenced... if you are pessimistic about the capacities of your students to know and learn then feeding them the party line is, to you at least, the best way to protect them.
But we as educators can and must believe that our students — and
everyone else! — is capable of more than this... attaining intellectual maturity requires immersion in the rough waters of public debate, which is exactly what Wikipedia is. The real danger of Wikipedia is its use by people made gullible by a system which promises them that someone, somewhere knows The Truth.
I’ve had ten hours of sleep in the last three days, and I just ate my first proper meal since Saturday. My inbox is clogged with messages I may never read. I am tired, but happy.
The Wikipedia blackout is over. Our goal was to raise awareness about SOPA and PIPA and to encourage readers to make their voices heard — and we’ve been successful on both counts. More than eight million people used our look-up tool to find their elected representatives, and millions more made their voices heard on social media. Thousands of journalists wrote news stories featuring the Wikipedia blackout screen.
We’ve made history together, all of us. And I think it’s important we understand what’s happened here, because the ground has just shifted under our feet.
Journalists see this as a conflict between old media and new media. They are wrong.
They see it that way because it fits with how things normally work.
“Right now, if you want effective legislation around your industry, then you need to pay the right lobbyists, make the right campaign contributions, and write the right legislation at the right time in order to get it out of Washington,” says Clay Johnson, formerly of the Sunlight Foundation. “If you had to objectively pick the winning team in Washington, pick the team with deep pockets and great lobbyists, not the team with community organizers and signed petitions. … It sucks, but those are the rules of the game.”
That’s precisely why MPAA chair and former longtime senator Chris Dodd called the blackout an “abuse of power,” and characterized it as “technology business interests resorting to stunts that punish their users or turn them into corporate pawns.” He can only see the issue as a clash of moneyed interests, because that’s how things normally have worked.
That’s why NPR, the Associated Press, Fox News – all label this fight as Hollywood versus Silicon Valley. It’s why stories like this one from Bloomberg compare how much money television, movie and music companies are spending in Washington, versus what Google and Facebook are spending. People are imagining that post-blackout we are playing the same game, just with new participants.
That’s not what this is.
There’s a lovely Clay Shirky talk floating around the Internet today. In it, Clay says what’s at risk with SOPA and PIPA isn’t just websites, or website owners: it’s our ability to share things with one another, as individual human beings. We are the people, Clay says, that SOPA and PIPA aim to police, because the biggest producers of content on the Internet are not Google and Yahoo. It’s us.
We know that’s true, because the people who led the blackout yesterday weren’t the CEOs of Google or Yahoo or Facebook or Twitter. It wasn’t the Wikimedia Foundation. The blackout was led by ordinary Internet users. At its centre were people like Osarius and SiPlus and FT2 and Titoxd and Fluffernutter. These are the people at the forefront of online content creation.
Wikipedia’s involvement in the fight against SOPA proves this wasn’t about powerful interest groups, and it wasn’t about money. Wikipedia is operated, and not controlled, by a non-profit — it’s got no corporate interests to protect and it doesn’t make any money from piracy or copyright infringement. It’s written by ordinary people. Reddit is a bunch of people sharing links and talking about them. Metafilter is the same. Tumblr, Craigslist, the Cheezburger network, The Oatmeal, 4chan, identi.ca. These are not mega-corporations.
The Internet has been giving ordinary people access to the means of production for more than fifteen years. Sometimes we use it to create pictures of cute cats. Sometimes it’s the world’s largest encyclopedia. Sometimes, we bring down corrupt regimes.
What happened yesterday is that around the world, Internet users found their voice — fighting back against people who wanted to threaten their freedoms. It is true that copyright infringement poses a problem, and it’s reasonable that those affected want to get their problem solved. But their problem is not more important than the ability of ordinary people to express themselves, to share and to learn.
It sounded today like Congress is starting to come back to technology firms and their users and ask what they want. What compromises to SOPA and PIPA would be acceptable. Would OPEN work. Do they need to draw up something new.
The message of the Wikipedia blackout, and the other responses to SOPA and PIPA, wasn’t “Let’s talk about how we can combat online copyright infringement.” It was: “Don’t hurt the Internet. It’s too important. Let us do our work. Let us learn and create and share.”
I want to thank everyone involved with the blackout. Below is a quick list of people I worked with, or saw working. If you helped but you’re not named here, please consider yourself thanked :-)
In completely random order: Dario Taraborelli, Lori Phillips, Moka Pantages, Nicholas Bashour, Luke Faraone, Jan Ainali, Puki, André Savik, Dcoetzee, Vituzzu, Stacey Merrick, Dan Rosenthal, Michael Snow, Sumana Harihareswara, Wikitanvir, Jim Redmond, Kaganer, PeterSymonds, Mikołka, ZeaForUs, Spiritia, Iliev, Anubhab91, Ali, Haidar Khan, Joan manel, Davidpar, Cameta, Mormegil, Okino, Sir48, Giftpflanze, Rbmj, Tecsie, BreadMaker, Antonorsi, Mariadelcarmenpatricia, Huji, Tommikovala, Nikerabbit, Lamiot, Seb35, Zetud, Amire80, Rekp, איש המרק, Eranb, עידן ד, Trần Nguyễn Minh Huy, Itzike, Vibhijain, Ruy Pugliesi, Roberta F., Tgr, Kelly Kay, Pagony, Alensha, William Surya Permana, Gombang, Gregorovius, Civvì, Gnumarcoo, Austroungarika, Miya, Whym, Takot, Melberg, Omshivaprakash, Idh0854, Freebiekr, Diagramma Della Verita, RajeshPandey, Mathonius, Romaine, Mwpnl, Whaledad, Wpedzich, Sp5uhe, Przemub, Ency, Przykuta, Teles, Vitor Mazuco, Lvova, OC Ripper, Euriditi, Maduixa, Wikiwind, Јованвб, A1, Олег-літред, Violetbonmua, Prenn, Cheers!, Sameboat, Tbayer (WMF), OhanaUnited, Tom Morris, Wdchk, Sarah Stierch, Risker, Billinghurst, NuclearWarfare, Jimmy Wales, Orionist, Ryan Kaldari, John Du Hart, Aaron Schulz, Kat Walsh, Cherian Tinu, Mike Godwin, Jim Burger, David Gerard, Johnuniq, James Forrester, Prodego, Fluffernutter, Dana Isokawa, Fae, Andrew Lih, Brandon Harris, Jeremyb, Michelle Paulson, DeltaQuad, Pete Forsyth, Fetchcomms, Heather Walls, Rachel Farrand, CMBJ, Erik Moeller, Fifelfoo, James Alexander, Itzik Edri, Katie Horn, Iván Martínez, Matthias Schindler, Ben Hartshorne, Jon Davies, Anthere, Slobodan Jakoski, Victorgrigas, Dimce, Jerry-Yuyu, Patricia Morales, Stephen LaPorte, Varnent, Lennart Guldbrandsson, Neil Kandalgaonkar, Greg Maxwell, Ian Baker, Jeandré, Howie Fung, Ryan Faulkner, Beatriz Busaniche, Philippe Beaudette, Ziko van Dijk, Oliver Keyes, Dimce Grozdanoski, Keegan, André, Guillaume Paumier, Maggie Dennis, Mentifisto, Phoebe Ayers, Arne Klempert, Mike Peel, Gorilla Warfare, Geoff Brigham, Swarm, Peter Gehres, Megan Hernandez, Leslie Harms, Tomasz Finc, Pretzels, Jay Walsh, Whenaxis, Liberaler Humanist, Sam Klein, Andrew Gray, Fifelfoo, Zack Exley, Katie Filbert, Victor Vasiliev, Guy Chapman, Avi, Kenneth/MD, Stu West, Harry, Ryan Lane, Josh Lim, Matthew Roth, Richard Symons, Gayle Karen Young, Yuvaraj Pandian, Evangeline Han, Milos Rancic, James Hare, Adrienne Alix, Samat, Tomasz Ganicz, FT2, Alessio Guidetti, Galileo Vidoni, David Richfield, Alison Wheeler, Siska Doviana, Erlend Bjoertvedt, Анастасия Львова, Steven Walling, Casey Brown, Tim Starling, Patrick Reilly, Arthur Richards, Asaf Bartov, Alolita Sharma, CT Woo – and of course, the 1,800 English Wikipedians who made the decision to black out the site.
I am happy to add new names to this list — if you want to nominate anyone, just say so in the comments :-)
Thanks also to the sister projects that chose to support the enWP blackout with their own protests: the Albanian Wikipedia, Arabic Wikipedia, Bulgarian Wikipedia, Catalan Wikipedia, Chinese Wikipedia, Croatian Wikipedia, Dutch Wikipedia, Georgian Wikipedia, German Wikipedia, Greek Wikipedia, Japanese Wikipedia, Korean Wikipedia, Indonesian Wikipedia, Italian Wikipedia, Norwegian Wikipedia, Portuguese Wikipedia, Russian Wikipedia, Serbian Wikipedia, Spanish Wikipedia, Swedish Wikipedia, Ukranian Wikipedia, Vietnamese Wikipedia and Wikimedia Commons.
Sue Gardner
Executive Director, Wikimedia Foundation
Three cheers for participatory democracy! The percentage of stated opposition to SOPA and PIPA in Congress changed dramatically over the past two days, from 28% to 61%. [If you count people who are "leaning No", by ProPublica's estimate, this goes up to 69%.]
How many politicians announced they would be co-sponsoring or otherwise outright supporting SOPA/PIPA on Wednesday? By our count: Zero.
Update: Harry Reid releases Dems in the Senate to vote against PIPA if their conscience demands. And Chris Dodd, former Senator and current MPAA Chairman, just called for a summit between Internet and traditional ‘content’ companies, convened by the White House, to reach a compromise. (He hasn’t yet realized that major content companies today are Internet companies.)
We are experiencing the growth of social unity and a certain moral sense across the Web, among people who have found something wonderful, worth defending with all their heart. This is a small piece; it is thrilling to be part of it. I hope you feel it too.
Below is an opinion piece written by Steve Virgin, a UK Wikipedian. It was originally published in the New Statesman.
Over the last few weeks, the Wikipedia community has been discussing proposed actions that the community might take with relation to proposed legislation in the United States called Stop Online Piracy Act (SOPA) in the House of Representatives, and the PROTECTIP Act (PIPA) in the U.S. Senate. If passed, these would seriously damage the free and open Internet, including Wikipedia. With more than 2,000 Wikipedians commenting on this legislation from all over the world, and a clear majority in favour of taking action, this was the first time the English Wikipedia has ever staged a public protest of this nature, and it’s a decision that wasn’t lightly made.
It was felt that both SOPA and PIPA are pieces of clumsily drafted legislation that are dangerous for the internet and freedom of speech. It provides powers to regulatory authorities to force internet companies to block foreign sites offering ‘pirated’ material that violates U.S. copyright laws. If implemented, ad networks could be required to stop online ads and search engines would be barred from directly linking to websites ‘found’ to be in breach of copyright.
However, leaving to one side the fact that there are more than enough adequate remedies for policing copyright violations under existing laws, in most jurisdictions, these draft bills go too far and in the framing SOPA and PIPA totally undermine the notion of due process in law and place the burden of proof on the distributor of content in the case of any dispute over copyright ownership.
Therefore, any legitimate issues that copyright holders may have get drowned out by poorly-framed draconian powers to block, bar, or shut down sites as requested by industry bodies or their legal representatives. Copyright holders have legitimate issues, but there are ways of approaching the issue that don’t involve censorship.
Wikipedia depends on a legal infrastructure that makes it possible for us to operate. This needs other sites to be able to host user-contributed material; all Wikipedia then does is to frame the information in context and make sense of it for its millions of users.
Knowledge freely shared has to be published somewhere for anyone to find and use it. Where it can be censored without due process, it hurts the speaker, the public, and Wikipedia. Where you can only speak if you have sufficient resources to fight legal challenges, or, if your views are pre-approved by someone who does, will mean that the same narrow set of ideas already popular will continue to be all anyone has meaningful access to
All around the world, we’re seeing the development of legislation intended to fight online piracy, and regulate the Internet in other ways, that hurt online freedoms. Our concern extends beyond SOPA and PIPA: they are just part of the problem. We want the Internet to remain free and open, everywhere, for everyone.
Ah, the luxury of seeing the media storm coming. That said, I was expecting it Wednesday and the phones started ringing the moment the warning banner went up on Tuesday. The UK press volunteers managed most of what we were asked for, though we had a shortage of faces for television — cheers to Steve Virgin, Jon Davies, Roger Bamkin, Martin Poulter, Mike Peel and of course Jimbo.
I spent two days doing radio. The analogy I bludgeoned into the ground (nicked from Cory Doctorow): “Banks notice that bank robbers use cars for getaways. Their solution: we have to ban cars. You say that’s ridiculous and damaging and won’t work anyway. They say ‘YOU JUST LIKE BANK ROBBERS!’” I’m told I suitably scared people on Radio 4 PM (38:50 on) with the consequences for UK business, though I could have done better. (Must not engage with the lying RIAA bullshit. Must not engage with the lying RIAA bullshit. Just repeat the soundbites. Must not engage with the lying RIAA bullshit.)
(If you’re an experienced UK Wikipedian who thinks they could acquit themselves reasonably well and have no problem with being a very minor public figure, please make yourself known on the wikimediauk-l mailing list and/or local meetups and you may get lined up for next time stuff explodes, the press want a random Wikipedian, etc. And feel free to casually talk to your local media about Wikipedia as the occasion arises.)
I’m amazed that several hundred Wikipedians largely agreed on anything at all. The Wikipedia community will fiddle around the edges of an issue forever and then not do anything. If you say to a bunch of Wikipedians “the sky is blue”, they’ll come back with a hundred pages of referenced counterexamples. The key skill to being a Wikipedia editor appears to be generalised cross-domain bikeshedding.
I hope we don’t do this, or anything like it, again any time soon. Our power requires not being used very often at all. But then: if Wikipedia says you suck … you really, really suck.
Today, together, the Wikimedia community did a really powerful thing. We raised an incredible amount of awareness about an issue critical to achieving our vision.
More importantly, we demonstrated once again the power of our community model. The thousands of you who participated in the community RfC. The volunteer administrators who helped crystallize our consensus. The incredible design, engineering and operations teams which implemented massive changes to world’s #5 web site less than 30 hours after the community’s decision. The editors who honed messaging. The lawyers who helped navigate so many tricky issues. The communications teams globally who spoke and wrote hundreds of times in support of our goals today and of our broader mission.
I have never been more proud to be a part of our community. Today we came together. Staff, volunteer, it didn’t matter. We all did it together. We are all the community.
Our work isn’t done. The principles (and money) behind SOPA/PIPA won’t just go away. Politics doesn’t work like that. And we have a few other challenges. Getting free knowledge to more people (500 million people a month is nice, but it’s just a start). Getting and keeping more new editors. Seeding Wikimedia communities in places they haven’t developed on their own. And many more.
But those are for tomorrow.
Today, let’s celebrate the fact that, eleven years after the birth of Wikipedia, the Wikimedia movement is stronger than ever.
-s
============================
Stuart West
Proud Wikimedia Board Member
stu<at>wikimedia.org
Over a dozen Congressmen have changed or clarified their position on PIPA and SOPA over the course of the past 36 hours, towards opposing the bills. This includes six senators and two representatives who had previously been co-sponsors or solid supporters of the relevant bill in their chamber. Many more who formerly were neutral about the bills or leaning towards opposing them, are now calling them “misguided”, saying they will “cause more harm than good”, “harm free speech rights”, “weaken freedom of expression on the Internet”, and would “harm Internet innovation and jobs”. Most agree that the bills as written “need to be stopped”. It seems that some of them have looked at the bills with a magnifying glass for the first time.
Senator Boozman summarizes: “Over the past few weeks, the chorus of concerns over Congressional efforts to address online piracy has intensified“. A week ago it looked like there might be a straight 60-vote approval of PIPA in the Senate; now it is losing suppoters by the hour, and may have a hard time getting majority support; making it unlikely to make it to a vote at all.
Blackout impact
Politico and others suggest that much of this movement was a direct result of the strong online statement made by the EFF, Reddit, Google, Wikipedia, and others – and the protest organized by those groups to express their views to every representative and senator in the country. Wikipedia produced a ‘find your local representative’ widget, to ensure that we encouraged readers to call their representatives directly; Google simply encouraged signing a petition.
Once the blackout launched, it trended worldwide on Twitter, with hashtags such as #factswithoutwikipedia, #SOPAstrike and #wikipediablackout. At one point, according to Trendistic, #wikipediablackout was used in 1% of all tweets. Hotspots claims that SOPA (and #SOPA) has accounted for a quarter-million tweets an hour since then.
The EFF reports that by 5pm, over 250,000 1 million people had contacted their representatives through the EFF blacklist site. Wikipedia reports roughly 160 million people have seen their blackout page, and eight million of those have looked up their elected representatives’ contact information through its tool. (No word on how many made contact; if there is a dropoff rate similar to the first clickthrough, then that would make another 400,000 contacts.) Google reports gathering 4.5 million signatures on its petition.
Statements today from members of Congress:
Senators noting their disapproval of PIPA yesterday and today: (those who switched away from previously indicated support are listed in bold)
Senators who changed from support, to advocating a delay in voting for revision and reconsideration:
House Representatives stating disapproval or opposition: (those switching away from previously indicated support or cosponsorship again in bold, but this was harder to ascertain):
A doff of the hat : Much of this data comes from or was confirmed through ProPublica‘s excellent timeline of public statements by Congressmen about SOPA and PIPA.