There is a flaw in this analogy that none of the sibling posts seem to have picked up on: only one person can (legally) display a given number plate / be in control of a car at once, whereas multiple people can and do share IP addresses. A better analogy would be "just because a person is on a bus does not mean they are guilty of infringements committed on that bus."

What's wrong with socialism? It seems to be working fine for the Nordic countries.

Nope, wheezy is on 3.2, which is still comparatively ancient given that Ubuntu is on 3.5.

If you're going with KDE, I'm not really sure what the point of going with Mint is, other than to avoid Kubuntu. FWIW, I use switched from Kubuntu to Debian with KDE and have no regrets.

There's not much that needs to be ported, really. All the Ubuntu-specific stuff is in userspace, so it can be used as is or with a recompile at most. The bit that differs between phones is the kernel, and that's where the bulk of the effort will be in targeting other phones (either in modifying the Android kernel to function like the mainline Linux kernel, or merging the drivers into the mainline kernel).

I never said that they made the decision for that reason; simply that that was the reason it happened. If KDE had used C, it's likely that many of the people drawn to Gnome during its formation would have been those who preferred C++.

The GTK community was created around that very notion. KDE pre-dated GTK, but used the Qt framework which at the time was published under the controversial QPL (it wasn't until 2000 that Qt was published under the GPL). GTK arose partly as a response to this, and since KDE used C++, using C mitigated the risk of the two projects competing for developers.

The more two competing open source projects use the same technologies, the less distinct their identities. Whether this is a good thing or not depends on how much diversity you prefer.

Try something KDE-based - they've had resolution independence for a while.

It's quite telling that my initial reaction to this article was, "I wonder how KDE Plasma Active runs on mobiles..."
Personally, I far prefer Debian's take on KDE to Kubuntu's.

Maybe it's just me, but clicking on the links / icons does nothing. Admittedly, this is on my desktop, but you'd think that it would here too...

Browser: Chromium 22.0.1229.94 Debian 7.0 (161065)

Such clauses may not be unenforceable under the Competition and Consumer Act 2010's unfair terms provisions.

(This is not legal advice, I am not a lawyer.)

I have a 3 tiered backup solution:
-my desktop and laptop use btrfs as their primary filesystems and take daily snapshots
-once a week the latest snapshot is copied to my server, which has a 4 disk Btrfs RAID* array (singly redundant). This is currently done using rsync, but will eventually use btrfs send once my kernel supports it (Debian user stuck on 3.2 here - any one have any idea when the feature freeze will end?)
-twice a year the server is backed up to some external hard drives

Btrfs provides integrity checks, snapshots, and faster RAID recovery times. Admittedly, it's still in development, but there haven't been any critical bugs in a stable kernel for a while AFAIK.

*I know RAID isn't backup, but what RAID is good for is minimizing the cost of a failure. Normally that refers to downtime, but in this case it's about preventing loss of the data saved since the last offline backup.

Github is officially denying that the search feature being killed has anything to do with the exposure of keys. They also have a link on the same page to information on how to purge keys from your repository. (Make of that what you will.)

Thanks, but we're here for a science lesson, not a history one.

I'll second this. That said, I'd settle for the ability to reply to HTML emails without totalling the formatting, given that it's pretty much the only reason that I have to use an alternative these days.

(Not sure if this is fixed in a later version - I'm on Debian, so I'm still using 4.4 because of the feature freeze.)