My apologies, I should have said SUBPOENA.

I don't disagree that all pertinent evidence should be gathered to prove or disprove a case, but the correct course of action here is for the judge to issue a warrant to the respective carriers/sites for the necessary information. Asking for someones passwords for evidence is like asking for someone's ATM PIN code to get their financial records.

+1

I took a consulting job with a medium sized services firm when i first moved into a new town and ended up gaining an insane amount of product experience and got to know hundreds of people. After about 4 years of consulting, the amount of effort got old and i took a server job for a company that was happy to grab me quickly (after taking one look at my resume and having a good interview). That job paid me almost double the job that immediately preceded the consulting experience.

I didn't get the warning in time and upgraded. Turns out I'm affected and hadn't even nailed down the issue until I saw your post. It not HORRIBLE per se, but it is mildly annoying. It manifests itself as a momentary system lock up, kind of like what happens when you run out of RAM and start swapping to disk. It's not continuous, there are periods of heavy occurrance, and of light occurrance.

Should be fixed soon it sounds like. It's tolerable for that period of time.

Though I'm against vigilante justice, I certainly agree with their motives.

HOWEVER.... Am I the only one who thinks Anon won't have much success? The worst they could probably do hack some user accounts. If they think DDOS'ing a site with the infrastructure to handle hundreds of millions of users is going to work with a bot net made up of a few hundred thousand machines, then they're probably in for a surprise. Heck didn't they already try and fail with Amazon?

Or was that Lulzsec? I get those two confused all the time.

The encryption itself is solid. What falls most of the time is the specific implementation. Say for example I made the choice to encrypt my hard drive but didn't use an already baked system like Ubuntu's home drive encryption. Instead I decided to do it by hand and code my own pre-boot initramfs to automatically handle decryption by hashing some hardware specific identifier from the bios. Except that since I'm not a security expert, I made some foolish coding error which allowed the hash to be intercepted or easily guessed. Then some hacker comes along, figures it out and now has full access to my encrypted data.

In this case the encryption itself is sound, and wasn't cracked, instead my shotty coding and/or lack of solid security knowledge was exploited. 9 times out of 10 this seems to be the case when encryption is defeated (brute forcing aside of course).

To answer your question though, why should you trust HTTPS? I'd say that you can never be 100% sure, but HTTPS has been around long enough to have been well tested by by people who rely on it being solid (banks, etc) that you're probably pretty safe. Rest assured that if HTTPS's implementation of encryption were cracked, it'd be news, and you'd know (I assume).

I'd just like to add for those readers not in the know that Android uses Apache licensing. They're not required to publish any modifications to Android, only to the kernel since it's GPL and not Apache. As such, it's highly likely that we'll never see the entire ROM's source code.

I like how this is all a robot's fault. As if these dozen robots are all flying around the busted well using an AI from the future to do work autonomously.

How about we tell it like it is. Some dude/dudette piloting an underwater submersible accidentally bumped into the well and did damage, and that damage required uncapping the well to fix.

More incompetence from the folks at BP. Nice spin job though.

Disclaimer: I harbor no hostility towards the pilot. It's BP who continuously makes bad decisions about how to handle a situation (such as putting too many bots in the water, or having them piloted by people not skilled enough to handle the situation) and the covers it up by blaming something else.

Sheesh.

Hate to burst your bubble, but DisplayPort is just as DRM encumbered. You may be thinking about the fact that DP is royalty free, whereas HDMI is not.

This might be a perspective thing, but I read "Company X has patched a record number of security holes" as a negative thing, not as something the OP or company X is reporting to gloat about. I've taken the liberty of reading the links by the OP (shocking, I know), and didn't find any of them to really be coming across as something that anyone is looking for a pat on that back for (and for the record, I didn't see an official comment from Apple on their "record patch job").

Fundamentally, you're right though. It'd be nice if companies could make flawless products, but it seems to be the exception rather than the rule, and when any company addresses a record number of fixes to a product's flaws, I see no reason why it shouldn't make the news. Granted, some fanboys will try and spin it into a positive of some kind, but that's not really shocking and we all know how trustworthy fanboys are.

My $0.02.

Care to place a friendly (or unfriendly) wager on that? Though I don't own a google phone, I'd say it's safe to say my distinct feeling is quite the opposite.

Motorola alone sold a million Droids in only a few months, and the growth (in sales and mind share) that Android has seen in the year or so it's been out it's actually quite surprising. I hate to say it, but I'd almost compare it to Windows on the Desktop. Almost certainly there are a fair share of fanboys and anti-fan boys out there, but the vast majority of users don't give a rats ass and just use what they know.

My distinct feeling is that Android becomes heavily commoditized and ubiquitous (because any phone manufacturer can use it for free, and customize it to their liking rather than pay some huge amount to develop and maintain their own operating system). Because of that, it becomes wildly available and consumers just end up using Android by default because it's what their shiny phone that they picked out in the store came with. Granted, I don't see ubiquity happening in the short term, but I'd expect it to become more prevalent as smartphone market share nears and eventually passes "dumb" phone market share.

Now before the Apple fan boys chime in here and wave their smartphone majority flag, I'll clarify that I see the Apple shooting themselves in the foot by limiting themselves to one basic model (the iPhone) while being the sole provider of it (and limiting what network you can choose). Let's face it, most people holding iPhones right now (myself included) are likely geekier than the general population and tend to be early adopters of consumer electronics. That's a LIMITED market compared to the much larger market of cell phone users in general

The iPhone really is the Model T of cell phones. There's very little customization, and as soon as everyone gets over the shock of something new (i.e. a mass produced combustion vehicle, or a snazzy smartphone), The competition is gonna eat you for breakfast by catering to consumer demand.

But hey, that's just one man's opinion, about as equally valid as your own.

Absolutely! Linux on the desktop does share many of those common points. The key thing that distinguishes the two is that (in my opinion) Linux on the desktop doesn't actually compare well to Windows from a user's perspective. Unfortunately one of the major factors when deciding between the two is a dependency in what a person is used to. Fortunately, Android has FAR less of a battle to win in the smartphone space given how relatively simple phones are compared to computers and how poor Microsoft's offering is compared to the rest of the market.

It's only a matter of time before Android takes over top market share for smartphones, the only real question is how long it takes. Now before you start screaming fan boy, bear with me here.

- Android is free
- Android can run on almost any piece of modern hardware, on any carrier (you listening Apple? probably not.)
- Every major carrier and every major smartphone maker either already has an Android phone, or has one in the works
- Being open source, carriers and smartphone makers can customize it as little or as much as they want
- Once smart phone makers are hooked on free, the only reason to dump Android is if there's a better mobile phone operating system out there that's worth the cost. Tough to do considering Android will be constantly approved upon given it's open source. Seriously, why dump Android to pay a per unit license fee when Android can do everything most smartphone users want their phone to do (and more in some cases)?

Some disclaimers apply here:
- No I don't have an Android phone, but yes I've used it enough to be familiar with it (including 2.0).
- I don't think its 100% there yet, but it's not far.
- Apples UI design is definitely better.

I'm sure some will disagree with me, and that's fine. Obviously this is my opinion and a guess. If you're looking for some ammo though, I use a Pre, switched from an iPhone and am pretty darn happy with it.

Why is Microsoft farming out the programming of a relatively simple tool when they have 10s of thousands of programmers and consultants on their payroll? Issues like this are exactly why you shouldn't outsource work when you already have employees that could do the job.