Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

October 10 2010

United Airlines learns geography

Of all the people I thought I’d be teaching geography to, I didn’t think it would be an airline.

So I requested retroactive mileage credit for two flights. One of them went through, and the other came back with “origin or destination is invalid”. I thought this was a bit odd, so I sent them the boarding pass.

To whom it may concern,

I requested retroactive Mileage Plus credit for two connecting SAS flights on July 14, SK 811 (OSL-LHR) and SK 4790 (GDN-OSL). Thank you for crediting my account with 751 miles for my flight from Oslo to London Heathrow.

Unfortunately, SAS has declined the credit request for SK 4790, giving the reason “THE ORIGIN OR DESTINATION IS INVALID. REVIEW AND SUBMIT THE CORRECT DOCS FOR THE FLIGHT”. By way of documentation, I have attached a photocopy of the denial letter and of my SAS boarding pass for the flights in question.

Please feel free to contact me if you require further information.

Thank you for your consideration,

Andrew Garrett

After about two weeks (quite promptly, actually, considering it was an international letter), I got this reply.

Hello Mr. Garrett,

Thank you for your recent letter.

Due to government restrictions flights flown on SAS within Norway do not earn frequent flyer miles.

I appreciate the opportunity to clarify this matter.

Regards,

K** G**

Well, that’s a bit weird.

Thank you very much for your prompt clarification.

Unfortunately, I am still confused, as Gdańsk is in Poland, not Norway.

Kind Regards,

Andrew Garrett

To United’s credit, I did get this the next day. No word on whether or not United pilots are now issued with maps.

Hello Mr. Garrett,

I have credited your account with the flight referenced in the email.

I appreciate you taking the time to contact me.

S** H**

March 20 2010

Getting ready for Berlin

So I’ve just confirmed today that I’ll be attending Wikimedia Deutscheland’s second annual developer conference in Berlin, during mid-April.

I’m super-excited about catching up and going out with everyone, and then getting together and doing some really awesome things to MediaWiki by day. I know from my experiences in Buenos Aires last August and in Paris last November that when you get a bunch of developers in the same place at the same time, you can get all sorts of amazing things done.

I’m hoping that I’ll be able to spend 15–20 minutes showing off LiquidThreads to a wider developer audience, and getting some feedback. It’s also going to be great to see how Chad’s new installer, and Ævar’s mapping stuff is going (to name two projects off the top of my head). We’re also going to talk about some new stuff, like metadata handling, better support for dumps and subscriptions, OpenID/OAuth implementation, and much more.

I’ll also be glad that we’ll be able to talk about some of the boring (but really important) issues facing MediaWiki development, like bug tracking, code maintenance, code review, unit testing and patch submission. It’s always great to get these issues sorted through, and the best way is to lock everybody in a room until we sort it out.

It’s going to be awesome!

December 16 2009

LiquidThreads almost ready to deploy

Hi all,

With the Foundation’s support, I’ve spent the last few months churning away at LiquidThreads, a new discussion system that is proposed for use on Wikimedia projects.

Essentially, it’s an attempt to marry the radical openness of the wiki paradigm with the usability and practicality of a forum-like system. As the name implies, LiquidThreads is designed to allow any user to easily refactor discussions while maintaining edit history, to edit other users’ comments, and to collaborate on a summary of an ongoing discussion. LiquidThreads also brings many standard communication features lacking from wiki discussion pages, such as watching and protecting individual discussion threads, RSS feeds of comments in a discussion or on a discussion page. In the world of online communication, its approach is entirely unique.

LiquidThreads has been in alpha testing on Wikimedia Labs for several months, and, more recently, it’s been used in a production context on the strategy wiki, where it has been quite well-received. It’s been easy to run these smaller trials, as the extension allows the activation and deactivation of LiquidThreads discussions on individual pages with a simple parser function.

While there are still some issues remaining before wider trials, I believe I can resolve most of them quite quickly (within a few weeks when my vacation finishes at the end of next month), and I’d like to get the ball rolling in proposing small-scale trials on some of the larger wikis, so that a full discussion can be had, and so that adjustments can be made on the basis of ongoing feedback. I’d especially like to see LiquidThreads used on some of the higher-traffic discussion pages on English Wikipedia (such as the technical village pump), and progressive rollout on some of our mid to large sized wikis.

So, I’d like to encourage you to have a play with LiquidThreads, either on the strategy wiki or on the test site (which generally runs a newer version). Tell me what you like about it, and (far more importantly) what improvements you think it needs before we can expand our trials to wider parts of the Wikimedia Universe, and perhaps move towards a full rollout of this very exciting technology.

I should give the following caveats about LiquidThreads as it stands. These are all issues that I intend to address before any trial expansion occurs.

  • Presently the system is somewhat vulnerable to abuse. I intend to make changes to the way signatures work, and improve tracking and listing of thread actions by specific users.
  • While LiquidThreads allows for thread summaries and discussion headers, the system does not currently have support for collaboratively-edited posts which are unsigned or signed by a group of people. These are a key piece of any decision-making framework, and I intend to make adjustments to make this possible.
  • There is no support for embedding LiquidThreads discussion pages on other pages.
  • There are plenty of minor interface issues which I intend to clean up.

Feedback is best directed to the dedicated feedback page, or, alternatively, to bugzilla (although before filing a bug, you should check the list of existing LiquidThreads bugs).

Thanks,

Andrew Garrett

December 07 2009

December 06 2009

November 30 2009

November 26 2009

November 24 2009

October 26 2009

MySQL, Ubuntu, Temporary Tables and AppArmor

I was trying to install CiviCRM on Wikimedia Australia’s server, and I came across this fun error:

ERROR 1005 (HY000): Can't create table '/tmp/#sql7013_9_0.frm' (errno: -1)

Turned out, Ubuntu’s AppArmor was breaking the creation of temporary tables in /tmp.

The way around this was to add a new line to the apparmor profile for mysqld
/tmp/** rwk

October 20 2009

Sex Offender Registration: The Facts

In an internet argument, I recently posted this response, built mostly from facts culled from Human Rights Watch’s report, “No Easy Answer“, on sex offender registration. It’s got lots of fun facts in it that might be handy, so I thought I’d post it here.

You can speculate and reason all you like (”once a pedophile, always a pedophile”, “most of the list is good, and properly utilised”), but have you checked the facts?

States such as Vermont and Minnesota have responsible public sex offender databases, in which a very small minority of registered sex offenders are actually placed on the website, which are those deemed to pose a real risk in communities in which they live.

There are good ways to maintain responsible disclosure of sex offender registration, requiring pro-active notification by law enforcement and restricting public register access to a need-to-know basis would prevent public humiliation of nonviolent sex offenders while informing people in a community when a member of the community poses a real threat.

30% of convictions for sexual assault resulting in a person being required to register as a sex offender are non-violent acts, not against children. 76% of people convicted for sexual offences do not commit any further offence. 5.6% of violent sexual assaults are committed by people who had never previously been required to register as a sex offender. People children know and trust are responsible for 90% of all sexual violence against children.

4% of youth required to register as a sex offender committed another sexual offence, and 90% of all sex offenders did not commit a sex offence while under 18. This isn’t a minority of sex offenders, 25% of those required to register as sex offenders are required to do so because of a crime they committed while under 18. 47% of offences against children under 6, and 39% of offences against children between 6 and 12 were committed by children who were themselves under 18. In terms of predictive power, the number of contacts with police for all reasons was twice as good a predictor as a single sexual offence of committing a further sexual offence.

There is significant evidence that the hardship imposed on those required to register as sex offenders increases recidivism in some cases, and makes tracking difficult (there are very few places in some states that registered sex offenders can live, so what do they put as their address?). Sex offenders are least likely to re-offend if they live with their families, have a stable job, and a place to live. Sex offender registration takes away all of these, by causing frequent public vilification causing employment dismissal, by imposing residency restrictions that prevent sex offenders from living with their families, preventing them from attending church services or receiving treatment and help for their condition.

Sex offender registration has, in several cases resulted in vigilante murders of people whose offences causing their registration as sex offenders were neither violent nor predatory, in many cases being streaking and public urination. This isn’t isolated, one third to one half of registered sex offenders lose their home, job or family. 16% of registered sex offenders are physically assaulted as a result of registration. Typical assault and harassment includes physical threats, ringing the doorbell in the middle of the night and leaving, leaving feces and garbage on the offender’s doorstep, up to being beaten or stabbed. In some cases, shots have been fired into registered sex offenders’ homes, injuring their family members.

Requiring sex offender registration for large classes of nonviolent misdemeanours has caused states such as California to literally lose track of 44% of its registered sex offenders.

Life registration is unnecessary and overly onerous, as recidivism rates decrease to 12%, 9% and 4% after five, ten and fifteen years of remaining offence-free respectively.

Contrary to what you might think, treatment is a solid method of reducing recidivism, reducing recidivism by 41% when modern methods are applied properly.

Community notification and online databases, according to a report by the Washington Department of State, have little to no impact on either the rate or location of recidivism, indicating that the online databases neither prevent recidivism, nor force it to go elsewhere.

So while I don’t oppose sex offender registration entirely (it can be done responsibly and with an evidence-based approach), its implementation in the United States is nothing but the product of a moral panic, which does not achieve its stated aims, and is based on received wisdom rather than empirical evidence.

October 16 2009

Tags: movie
Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.