Restricting cookies vs. using Google Hangouts

No idea if this is useful to anyone but it was an interesting exercise.

By default I have disabled storing cookies in my main web browser. I have a custom list of specific web sites that I allow to set cookies. (Whether that makes any sense regarding all the other data your browser sends which might create a unique fingerprint anyway is a different question up to your personal judgement/opinion on “privacy” and not the topic here.)

Ideally that whitelist would only include web sites that use my data in a way that I can agree with. In reality, services exist that could either be considered convenient (like Facebook; if you want to use their services you could use a private browser session every time and reenter your password, or use a separate browser to isolate Facebook’s cross-site cookie pollution) or services that your employer or customers use or expect for whatever reasons.

Google Hangouts video calls and Google Hangout text chats (which are proprietary after dropping XMPP) are used by some of my co-workers.
I have been wondering for a while which specific Google sites to allow setting cookies in order to be able to use these services but could not find information on the web. Google lists a bunch of domains but that list seems neither specific nor complete.
Going for trial and error, I removed any Google cookies (which might require more than a simple string search due to sites such as, removed any potential rules allowing Google cookies, set my browser to not allow any cookies, and see how far I can make it working around random error messages and getting logged out immediately after having logged in.

I ended up allowing the sites,, clients[1-6],, people-pa.clients[1-6],, to set cookies. Some of these were trickier to find but your web browser’s developer tools allow you to check which sites want to set cookies.

And now back to actual work.

Posted in computer, lang-en | 4 Comments

Rewriting code review documentation, on paper.

At Wikimedia, for the last months I’ve been on and off rewriting our on-wiki technical Gerrit/Git/Code Review documentation.

Code review related documentation

That included improving the onboarding steps like setting up Git and Gerrit (related task; 135 edits), the contribution guidelines and expectations for patch authors (related task; 28 edits), and to some extent the guidelines for patch reviewers (related task; 23 edits).

Among the potential next steps there is agreeing on a more structured, standardized approach for reviewing code contributions. That will require engineering and development to lead efforts to have teams follow those guidelines, to establish a routine of going through unreviewed patches, and other potential iterative improvements.

Printed documentation.

On paper

I’m not a person carrying around a laptop and don’t use mobile phones much. The more text/comments to tackle (or seperate pages covering related topics), the more I prefer working on paper. (That’s also how I started high-level planning the GNOME Evolution user docs rewrite.)
It might be archaic but paper allows me to get an overview of several pages/documents at the same time. (I could probably also buy more or bigger screens?) I can mark and connect sections that are related and should not be in four different places (like Troubleshooting related information or operating system specific instructions). Plus trying to be accountable and transparent I end up performing lots of small atomic changes with a proper change summary message so I can cross out sections on paper that are done on the wiki.
Paper especially works for me when thinking about topics that still require finding an approach. So I end up in the park or in a pub.

In a future blog post I’m going to cover what I’ve learned about aspects and issues of code review.

Posted in computer, lang-en, user-documentation, wikimedia | Comments Off on Rewriting code review documentation, on paper.

GUADEC 2016.

Filthy attempts on the unconference session scheduling whiteboard by so-called “friends” trying to trick me into literally ‘something’.
They won’t succeed.

#makeandrenevertalkagain #noicecreamleftbehind

Posted in computer, gnome, lang-en | Comments Off on GUADEC 2016.


Middle East

In late March 2016, I attended some Wikimedia gatherings in the Middle East: The WikiArabia conference in Amman (Jordan), a Technical Meetup in Ramallah (Palestinian territories), and the Wikimedia Hackathon in Jerusalem (Israel).

I gave an introduction to the many technical areas in Wikimedia anyone can contribute to. I also gave an introduction how to use Phabricator, the project management suite used (for mostly technical aspects) by the Wikimedia community which allows managing and following progress in projects and collaborating with developers.

As I love discussing society and politics I was not sure initially how much I’d have open and blunt conversations. But on the first evening I was already sitting together with folks from Tunesia, Egypt and Saudi-Arabia who were comparing the situations in their home countries. People also allowed me to learn a little bit about how daily life is in Iraq or Saudi-Arabia.



After a short trip to Petra, we spent an entire day to get to and cross the border between Jordan and the West Bank. If you look at the mere distance it feels ridiculous. It definitely makes you appreciate open borders.

At the border crossing between Jordan and the West Bank

At the border crossing between Jordan and the West Bank

Afterwards, we were very lucky that Maysara (one of our hosts) took the time and his car to drive us around in the Westbank to visit a bunch of spots, pass settlements, look at walls, or wonder which streets to take (sometimes a checkpoint with a soldier pointing a machine gun at you helps making decisions).

The old city center of Nablus

The old city center of Nablus

Graffiti on graffiti in Ramallah

Graffiti on graffiti in Ramallah

At some point, Maysara simplified it in a single quoted sentence: For Israelis it’s fear. For Palestinians it’s humiliation.

Street sign in the West Bank

Street sign in the West Bank

Imagery of dead fighters in Nablus

Imagery of dead fighters in Nablus

In Israel, we walked through Jerusalem’s old town, visited Masada and took a bath in the Dead Sea.

Dead Sea: Past war zones

Dead Sea: Past war zones

View from Masada

View from Masada (the squares were siege camps)

On the last day I visited the Yad Vashem Holocaust memorial with some co-workers (thanks to Moriel for organizing it). It’s obviously an activity you cannot “look forward to”. I am still impressed by our guide who explained and summarized history extremely well.
The architecture of Yad Vashem makes you go through several rooms on the left and right of the passageway in a chronological way and our guide mentioned several times that you “cannot yet see what is coming a few rooms (means: a few years) later”, and the question “Why did Jewish citizens not flee” got answered by “Where would you try to escape to if even outside of ghettos and concentration camps everybody is hostile”. Which explained very well the self-understanding why to found a state for Jews.

I am incredibly thankful to those many great people I could meet and who shared their points of views on the social and political situation, always in a pretty reflected and respectful way despite of all the frustration being around.
And whatever my question was to locals, the answer pretty much always was “It’s more complicated than you thought.”


Afterwards I spent some time in India to attend Rootconf, visit GeekSkool to learn a lot about why the concept works, and attend GNOME.Asia (thanks to Shobha and everybody organizing it!).

Hardware recycling via badge lanyards

Hardware recycling via badge lanyards

Breakdance competitions

Breakdance competitions

In a society where the path of welfare could be expressed by “walk → motorbike → car”, I received some grins admitting I had never had a motorbike ride before. In Indian traffic I’d call that an experience, for a tourist like me.

GNOME.Asia 2016 venue

GNOME.Asia 2016 venue

GNOME.Asia 2016 music

GNOME.Asia 2016 music

As usual, it’s wonderful to finally meet folks in person who you’ve only spoken to online beforehand, and to hang out with old friends. (I sound like a broken record here. I am sorry I could not see everybody. I’ll be back.)

Posted in gnome, lang-en, misc, non-technical, politics, wikimedia | Comments Off on Travel.

War Porn.

Photo of the book.

Sometimes, when some individual, group, institution publishes, releases, leaks a cruel video of this planet’s conflicts, media decide not to show it or only show a (edited) screenshot.
I usually end up trying to find the uncut video on the internet because I naively believe I can better realize how cruel things are when I force myself to watch it.
So I constantly feel the need to defend my behavior against accusations of voyeurism and dehumanization: “Can’t you imagine the rest anyway? Haven’t you played video games and watched enough fictitious movies?”

A few months ago I bought the photo book “War Porn” by Christoph Bangert (a photo journalist in war regions). The photos are somewhere between disturbing and disgusting.
Bangert also covers the aspect of self-censorship as a photographer or publisher, hence for some of the pages you have to decide yourself whether to break the perforation to see the image included on that page.

The book’s introduction puts it into simple words that I could not find myself:
“What’s the point of showing these things? We know that wars and disasters are horrible events. But are we really aware of just HOW horrible they are? Yes? Why are we so shocked by these pictures, then?”

Posted in lang-en, non-technical, politics | 2 Comments

Wikimedia in Google Code-in 2015

(Google Code-in and the Google Code-in logo are trademarks of Google Inc.)

Google Code-in 2015 is over. As a co-admin and mentor for Wikimedia (one of the 14 organizations who took part and provided mentors and tasks) I can say it’s been crazy as usual. :)

To list some of the students’ achievements:

  • More than a dozen of MediaWiki extensions converted to using the extension registration mechanism
  • Confirmation dialogs in UploadWizard and TimedMediaHandler use OOjs-UI
  • Vagrant roles created for the EmbedVideo and YouTube extensions
  • Two more scraping functions in the html-metadata node.js library (used by Citoid)
  • Many MediaWiki documentation pages marked as translatable
  • lc, lcfirst, uc and ucfirst magic words implemented in jqueryMsg
  • Screenshots added to some extension homepages on
  • ReCaptchaNoCaptcha of the ConfirmEdit extension uses the UI language for the captcha
  • MobileFrontend, MultimediaViewer, UploadWizard, Newsletter, Huggle, and Pywikibot received numerous improvements (too many to list)
  • Long deprecated wfMsg* calls were removed from many extensions
  • The CommonsMetadata extension parses vcards in the src field
  • The MediaWiki core API exposes “actual watchers” as in “action=info”
  • MediaWiki image thumbnails are interlaced whenever possible
  • Kiwix is installable/moveable to the SD card, automatically opens the virtual keyboard for “find in page”, (re)starts with the last open article
  • imageinfo queries in MultimediaViewer are cached
  • The Twinkle gadget‘s set of article maintenance tags was audited and its XFD module has preview functionality
  • The RandomRootPage extension got merged into MediaWiki core
  • One can remove items from Gather collections
  • A new MediaWiki maintenance script imports content from text files
  • Pywikibot has action=mergehistory support implemented
  • Huggle makes a tone when someone writes something
  • Many i18n issues fixed and strings improved
  • Namespace aliases added to MediaWiki’s export dumps
  • The Translate extension is compatible with PHP 7
  • …and many, many, more.

Numerous GCI participants also blogged about their GCI experience with Wikimedia:

The Grand Prize winners and finalists will be announced on February 8th.

Congratulations to our many students and 35 mentors for fixing 461 tasks, and thank you for your hard work and your contributions to free software and free knowledge.
See you around on IRC, mailing lists, Phabricator tasks, and Gerrit changesets!

Graph with weekly numbers of Wikimedia GCI tasks

Posted in computer, lang-en, wikimedia | 2 Comments

2015: Music.

Publishing my usual list of awkward and never complete pop music preferences of 2015.

Grimes’ “Art Angels” is probably my favorite album of 2015. Halsey’s “Badlands” debut and the latest releases by Purity Ring and Chvrches came close.

In general Angel Haze was the most dominant artist in my playlist. I also enjoyed Little Simz’ “A Curious Tale of Trials + Persons” debut and FKA Twigs’ “M3LL155X”.

Other helpful artists were We are Twin, Leftfield (with a surprisingly great 2015 release), Lowell, TĀLĀ, Camila Moreno, and Tei Shi, and Autobahn.

Posted in lang-en, music, non-technical | 1 Comment

Google Code-in 2015 has started!

(Google Code-in and the Google Code-in logo are trademarks of Google Inc.)

Another round of Google Code-in started yesterday. Together with Nemo and Petr I am one of the organization administrators for the Wikimedia community.

In this year’s edition of Google Code-in, students can choose from tasks provided by the following organizations / projects: Apertium, Copyleft Games, Drupal, FOSSASIA, Haiku, KDE, MetaBrainz, OpenMRS, RTEMS, SCoRe, Sugar Labs, Systers, Ubuntu, and Wikimedia.

If you are a 13-17 year old pre-university student interested in getting involved into free and open source software development, check out Google Code-in.
It is a great opportunity to learn about distributed software projects, to find out which areas of software development you are interested in, to gather some on-hands experience, to contribute to “real” projects out there used by millions of people, and to make new friends all over the world.

Posted in computer, gnome, lang-en, wikimedia | Comments Off on Google Code-in 2015 has started!

Prioritizing volunteer contributions in free software development

Wikimedia is an organization which has both volunteers and paid folks working together in software development, with many software projects and different stakeholders involved.
In Wikimedia, there is currently some discussion how to improve the code review process. One aspect is reducing our code review queues and waiting times, with a focus on contributions provided by volunteers.
There are numerous successful free and open source software projects with a similar setup of companies and volunteers involved (Mozilla, Openstack, …) so I’m curious if your project has also investigated similar questions and if there is some knowledge and experience to share.

  • In your project, do maintainers commit to review contributed patches in a certain timeframe, like “all patches receive a first review comment within four days”? How is this process implemented? Do you think it is successful?
  • With an existing backlog of patches that did not manage to attract a review, what do you with ancient and rotting patches? Do you just abandon them after a certain timeframe in your code review tool to get a “cleaner slate”? Or do you leave them open to (theoretically) allow someone to find them and them pick up?
  • Do you have any specific workflow in place that provides feedback to patch authors who contribute a patch to a rather unmaintained repositories that noone feels responsible for (anymore)? Do you signal the lack of maintainers and encourage contributors to step up as maintainers? How?
  • Do you have a workflow in place to specifically prioritize the review of patches contributed by volunteers? How efficient is it?

I’d be very interested in hearing how your project handles these issues. Needless to say, links to documents are welcome. Thanks!

Posted in computer, lang-en, metrics, wikimedia | 1 Comment

Wikimedia: Phabricator, Tech Community Metrics

Trying to quickly summarize what’s been either on my plate or what’s been generally cooking in Wikimedia, before I postpone writing that again…


Tech Community Metrics

Recently also spent more time with Tech Community Metrics. Wikimedia has some metrics about code repository activity (Git), code review activity (Gerrit, in the long run to be replaced by Phabricator Differential), mailing lists and IRC. It’s available at backed by MetricsGrimoire and supported by Bitergia. When we migrated from Bugzilla to Phabricator Maniphest we initially lost any statistics on bug tracker activity but now there is an initial Phabricator Maniphest backend in MetricsGrimoire available.
Again, all this is work in progress and needs way more fine-tuning (see our project workboard).
Posted in computer, lang-en, metrics, phabricator, wikimedia | 1 Comment