I know you were joking, but I'd like to make the following point anyway:

How long until we have fusion power is not a function of time, but a function of investment.
Insufficient/deacreasing investment results in increasing the amount of time needed to complete the required R&D.

In fact a Q&A here on slashdot covered this. It even provided the following graphic as clarification of "50 years until fusion":

I have a Debian HTPC system tracking testing and systemd tried to save from the indignation of PulseAudio. Given configuring ALSA for AC3 S/PDIF is not as easy as it should be, I let PulseAudio stay on my system.

Then came systemd and any application (Flash, KDE itself, VLC) would hang as soon as it attempted to output sound. "PulseAudio --start" instances would just multiply and multiply.

My girlfriend was somewhat annoyed that she couldn't watch her programmes, and trying to work out what was happening was getting to me too.

After battling PulseAudio and ALSA settings, I was started to question if it was a mistake to leave PulseAudio installed all this time. Systemd was trying to help me see my error.

However given my girlfriends mood and lack of patience, as well as the fact that everything worked before Debian switch my init system, I tried apt-get install sysvinit-core and reboot (mostly out of desperation). From that moment on we've had no problem with sound, PulseAudio nor any of the other 'bugs' that showed up recently.

Given my sense of humour, I find it hilarious that systemd seemingly broke PulseAudio. Beyond making me laugh it also induces a sense of nostalgia. As I was in Uni all those years ago, I remember playing CoreWars. This was a game where two users would to develop a programmes that tried to avoid and eradicate the other users program.

Up until I removed systemd I imagine a similar battle being waged on my HTPC. PulseAudio battling with PID 0 and spawning many copies of itself as protection. On the other side systemd using it ultimate control of the system to hijack dbus and udev in order to isolate PulseAudio and to prevent it from communicating with the outside world.

If it weren't for the non-amused look on my girlfriends face, I might have let the two battle it out. However as it stands PulseAudio has won, as systemd is no longer running on the system. Did good or evil win? We'll never know. Suffice to say during the whole affair systemd said nothing, not a single peep to stdout nor stderr.

With the close of google reader I switched to OwnCloud News running on my own hardware.

Pro: Not reliant on others, Con: I only have myself to blame if I go offline =)

In the US because of the Mickey Mouse Protection Act or rather the Copyright Term Extension Act.

Basically every time Mickey Mouse is about to go out of copyright and into the public domain, Disney lobby for copyright to be extended.

Given that they actively use MM, their Trade Mark on him will never expire. Isn't that enough? Why continuously extend copyright?

I have an instance of OwnCloud setup at home. I use it mostly for syncing contact and calendar data. I'm even subscribed to my girlfriends calendar and vice versa. The WebDav part I only really use as a quick way to get files from one device to another, and by device I mean smartphone, tablets as well as proper computers.

When Google announced the closure of Reader, OwnCloud started work on a news reader app too. I've been running it since the beta and I'm very happy.

Here is a rather long IRC discussion between the Wayland and a Mir developer(s) on why..

AFAI can tell, a year ago when Canocial/Ubutunu were deciding which way to go, they stopped believing that Wayland would mature into something that fits their grand plans. Instead of discussing these concerns with the wayland people, they decided to fork Android's graphic stack. (and thus be able to talk to all the ARM SoC blob drivers that support it).

So we're going to get one Unity/Mir/Ubuntu stack on everything from Phones to Desktops....

In the end none of their concerns about wayland turned out to be valid. Daniel Stone even has a compositor that does server-side buffer allocation and runs on said ARM SoC h/w. None of the insecure wayland input remarks on Mir's wiki are true, etc.. Not that it matters now, Ubuntu have already invested in Mir and will likely continue to do so; it will after all, being under their control, no doubt fit perfectly into their grand plans.

Most of the regex are qulified with a star *, which mean 0 or more times. So since the regex allows 0 matches I can put in whatever I like. Maybe they meant + ? I'm not going to look at the solution. I will just concentrate on the few chars that are not suffixed by a * .

See: http://packages.debian.org/search?keywords=linux-image

Debian dropped i386 kernel images a very long time ago; the lowest you can go is 486.
Annoying for me is, that they also dropped i686 without pae. Meaning for my AMD Geodes I either have to roll my own or install 486.

I am guessing that this is the Google TechTalk video that is discussed in the summary, but not linked (or more likely edited out): http://www.youtube.com/watch?v=4JuoOaL11bw

To enjoy the film, which I did, I had to actively ignore anything that was said in relational to IT. Something that I find hard to do.

The concept behind the plot, while at the most extreme of technical possibility, was a valid idea to explore in a piece of fiction. The Iranians would likely have never detected stuxnet if its 'herders' had kept a better control on its spreading. Imagine something like that in a western government (as the victim). No, what annoyed me most is that they didn't even bother. Simply swapping some of the IT buzzwords in the script for ones that actually meant something in the given context, would have greatly improved its palatability. However that would mean employing someone with real IT knowledge on the writing team. Such a person might have gone insane or have made the script 'boring' with too much attention to accuracy, who knows.

One theory I had when leaving the film, was that maybe the makers didn't want to give the general public any ideas or tips in how someone would go about achieving any of the anarchy portrayed in the film. The more misinformed about computer 'hacking' the safer we'll all be...

The two main complaints I see discussed here appear to derive from some fundamental misunderstandings about what Wayland is.

Wayland is a Protocol and an optional helper library to implementing that protocol. This protocol says nothing about net work transparency, in both the sense of enabling or prohibiting it. It also says nothing about client decorations. The key points here is not to make a decision for or against any particular technology or methodology and then be stuck with that decision for the next 20 years, like we are with X.

How or if, either of these work is all down to the compositor. The reference compositor 'Weston' does not do network transparency and leaves window decoration to the client or its toolkit. However none of the big desktops, i.e end users, will be using this compositor. For example KDE will continue to use Kwin as their wayland compositor, and KDE have already clearly said that Kwin will be decorating their windows and not the clients!

As to network transparency, all windows are drawn to their own back buffers, and where these buffers will be eventually displayed is also the choice of the compositor, and it might well just decided to send them over a network connection. e.g. like what VNC does.

I think if you base your opinion on what other people say, including me, then maybe you shouldn't comment? All of this is discussed first hand on the Wayland web site and/or mailing list.

Unfortunately since I've posted a bit late, I doubt many will read this...

Most people use the standard 4 digit pin, this pin unlocks the keys to the encrypted FS.

With physical access to the phone, one can brute force a 4 digit numeric pin in about 20mins. The brute force has to be done on the phone itself, because you can't access the keys directly, but rather the API of the crypto chip. So you boot your brute force boot image via DFU mode. This of course bypasses any wipe on X failed attempts settings that might have been set in iOS.

Alphanumeric PINs are a PITA, so I'd suggest using a 7 or more digit numeric PIN. This is done by turning off simple passcode and then entering a passcode with only numbers (dispite the full keyboard). When asked for the passcode again to unlock the iPhone will give the normal numbers keypad. (Telling a hacker that your pins only uses numbers, but also make your life much easier).

I am pretty sure the MicroUSB connector is now required in the EU.

Maybe a mircousb plug will fit it for USB and power, but the official Apple plug will have more contacts on it for other functions.

"In the final stage, 'all remaining issues will be tried, including damages and willfulness.'"

Wouldn't using the word 'wilfulness' suggest he already thinks Google did something wrong?
You or I may or may not think that, but a judge should try to remain neutral. Maybe a 'if needed be' or some such context was cut out of the quote.

Didn't the US push the EU to allow them to be able to downgrade the Galileo signal, effectively giving the US a Galileo veto?

At least that's my memory from, I think, 2004.