And looked like Blackberry, nothing like the iPhone or modern Android.

Out of curiosity, what is Apple not giving back? Other than the core user interface and windowing environment which is not surprisingly quite proprietary, most of OS X is available for download on their open source page, and if you work at it you can build a working Darwin system. I always get the feeling that people saying Apple doesn't give back have never actually looked.

There are numerous third party authorized service centers who will come to you. Because they are authorized they have the factory parts and tools, and the warranty is respected, just like if you sent it in to Apple. Going to the Apple Store or calling the number is not the only option.

There is an Omnibar extension for Firefox which will combine the url and search bar into one, just like in Chrome. It even supports the search suggestions.

Firefox's equivalent to Recently Closed is in the History menu, there is a Recently Closed Tab list. To open the most recently closed tab is Control Shift T.

Woah woah woah, a torrent?

I'm afraid I'm going to have to ask you to come with me. No, you cannot speak to a lawyer.

Of course I do. The Fridays waiters actually use the credit card!

The best part is Remus wasn't personally affected, other than possibly getting a new credit card. I could understand if Kevin Mitnick drained his checking account or stole his identity, but this is all based on a letter saying his account details were compromised, very possibly by somebody other than Kevin Mitnick. I've gotten multiple similar letters in the last year, most of them involving Anonymous and Lulzsec, and yet I really don't have an axe to grind against them either.

I would think 20 years later "Kevin Mitnick stole my credit card number" is a bragging right anyway.

You see wrong. Linus has already said, when kernel.org is back up completely, github will be just a mirror.

Windows will work, it just has to be configured beforehand to do so, specifically running Sysprep to tell Windows to expect to boot on new hardware, at which point it will perform what is essentially a partial reinstall in order to support that new hardware. It is not as plug and play as Linux generally is, but if done correctly works quite well.

Security is not the focus, this has been made clear.

Yeah, those do nothing for the archive files sitting on the kernel.org homepage.

They don't exactly go out of their way to draw attention to the fact that the signatures even exist, do they? The mention of signing is after the paragraphs of recent news, which most users are not likely looking at when they go to download the file. The .sign file is hidden in the file structure, no link on the main page.

The fact that they provide a nice, bold link to the current version without even a smaller link to its corresponding signature is a pretty big oversight. Even basic projects generally provide a link to at least an md5sum.

If the package signing key gets out in the wild, that is a problem. Aside from that, you cannot really have an issue where someone creates a fake package and gets it past a check, because they simply cannot generate the correct signature. SSL has a flaw that a browser will see "*.google.com" and trust it, even if it was not issued by the actual CA that Google uses. That issue does not exist with signed packages.

Also, when I go to kernel.org I generally see a lot of .tar.bz2 files for download. What's to stop an attacker from packaging a patched source and putting it in the place where most of the rolling release distributions are actually pulling it from? So what if the source tree is clean, if the packaged version is not then there was a problem.

No, it's not. All they have done is fixed their DNS so things like Akamai (and Google's own distributed system) can function as designed.

In the past if you switched over to Google's DNS or OpenDNS, you ended up with a slower Internet experience in some ways, as the CDNs would send data from the node located closest to the DNS server, rather than the client. If you were a user in Europe, you might very well be receiving a YouTube stream from within the US. This has changed, as the CDN can tell the location of the client apart from the DNS server the client is using and use the appropriate frontend.

None of this has been an issue for the normal ISP-provided DNS users.

Also of note is Akamai is not supported at the moment, so a large chunk of the CDN traffic is still broken. Also, Google's own DNS benchmarker, namebench, often shows better performance from ISP servers than OpenDNS or Google's, simply due to the location. If an ISP server is not misbehaving by hijacking typos and such, there isn't too much reason to switch (that I can see).