You don't need to take photos using an iDevice to have them end up in iCloud. All you need to do is use a Mac.

If you use a Mac to download pictures off your camera - including cell phones that aren't iPhones and therefore behave like standard cameras and don't require Apple-specific software - by default, your pictures will end up in iCloud. It's part of the "Photo Stream" thing to allow users to stream pictures to the Apple TV that clearly every Mac owner has.

Apparently (and I don't know that this is true as I don't use Twitch that often) you can't reduce it to a reasonable time any more. (Maybe it's changed?) All I know is that people I know who do stream games where they want to have audience participation (things like having the stream direct the choices they make in an RPG) have switched to using HitBox due to the amount of lag between when they do something and when the viewers see it.

For those not familiar with Twitch, every stream contains a "Now Playing: (Game)" thing with it, and you can select which game you're playing from a pre-defined list of games.

Bets on how long until that become a link straight to Amazon to buy said game, and how long until streamers become Amazon affiliates and start getting money for driving people to buy their games off Amazon?

Because that's the only angle I can see Amazon having here: trying to get gamers to grab games off Amazon. (And they do sell digital game downloads, so they do compete with things like Steam.)

Maybe Amazon can fix some of Twitch's more recent problems like the horrendous stream lag that makes it impossible for streamers to communicate with the stream chat since the stream now has something like 30 seconds of latency between streamer and audience. Then there's Twitch's new weird anti-piracy thing where they mute audio if they detect that the audio contains a copyrighted song (hint: for video games, that's always) and whatever other issues people are complaining about Twitch these days since I never bother to use it.

Worse, on BBC America, they actually edit out large portions of the show.

Remember that the original show is nearly an hour long without commercials. So for the US version, they edit it down to the standard 44 minutes so they can include 16 minutes of ads. Which means you're missing anywhere from 12-20 minutes of content depending on original. (Based on Netflix run times.)

They've started showing the initial airing of a new Top Gear in hour 20 minute blocks, but repeats are always the edited versions. There's some stuff that's simply never been shown on US TV because it was edited out for ads.

You left out the part where the flash forward is often misleading and designed to make the next part seem more interesting than it really is. So you start the show with an exciting preview, then a bit of content, then another exciting preview. Then ads. Then a recap, then the discovering that what looked interesting in the preview was entirely uninterested followed by another deceptive preview.

But MythBusters does it even more annoyingly: they'll combine Adam and Jamie doing Myth A with Tori, Grant, and Kari doing Myth B. So you end up getting those little recap, content, preview segments first for Myth A and then for Myth B, followed by a block of ads. It makes the entire thing completely disjointed and pads out what should be two mini-episodes into a single 45 minute episode.

I've kind of wanted to take a MythBusters episode as aired and edit it to remove the preview/recap stuff and merge Myth A and Myth B into a single block of content and see how much content I'm left with. Except I'm too lazy to bother pirating an episode to do that.

A lot of companies do. I have to have Java installed on my work computers - and not just because we end up writing a lot of Java code ourselves. The backup software IT uses requires 32-bit Java. (Not 64-bit, it will crash if you use 64-bit Java. Up until recently it would also crash if you used anything after Java 1.6, but since that's no longer supported, they finally fixed that.)

There are also a few internal sites that require Java applets, so that's fun to deal with too.

The article actually mentions this: that doesn't do what you think it does. All that does is sort the Top Stories feed in chronological order.

It's still the filtered view.

Just in case you weren't aware, all that does is sort the Top Stories chronologically. You're still only seeing the posts Facebook decides you want to see.

As far as I know, there is absolutely no way to prevent Facebook from filtering posts. If there is I'd love to know what it is, but Most Recent isn't it. (I think it used to be, but enough people knew about it, so Facebook had to take that away. We will read the ads Zuckerberg wants us to read, dammit.)

As another AC mentioned but I think deserves reiterating: that option merely sorts the Top Stories in chronological order. It does not show you all posts from all your friends. If Facebook has decided you don't want to see a post, you will not be seeing it. If they've decided you want to see fifty copies of various people posting some annoying Facebook quiz result even though you've hit the little "don't show me this" option a thousand times, well, you will be seeing fifty copies of that Facebook quiz. (After all, stupid Facebook quiz makers are important (paying) Facebook partners, and your friends are just more losers to show important (paying) Facebook partner content to.)

The only difference is that in Most Recent, they'll be in chronological order and not ranked by Facebook's "how much did the content publisher pay us?" algorithm.

Actually, yes, they do.

I once tweeted to complain that of the four Southwest flights I took, a single one managed to get me to my destination on time. Every other flight was late in some way. My "favorite" of that group was the flight that landed 20 minutes ahead of schedule, only to be refused a gate at the airport and had to sit around on the taxiway somewhere for 40 minutes before being assigned a gate. (Apparently Southwest doesn't rent enough gates for all their flights at Seatac.) This counts as an "early" flight as far as their metrics are concerned, despite the fact that everyone was stuck on the plane until 20 minutes after it was scheduled to arrive.

Second place goes to the flight which landed at a Southwest hub that was stuck on the taxiway because there was no ground crew available to bring the plane to the gate and connect the jetway. Again: at a Southwest hub airport.

So, in any case, I tweeted this using Southwest (intentionally not using @SWA because I didn't really care at that point since by then I was done traveling) and got a response from a Southwest customer service agent.

The answer is yes: they do, in fact, search Twitter looking for people talking about Southwest and will reply to complaints.

Other businesses do this too. I've actually managed to get tech support issues resolved by whining about them on Twitter without even mentioning the a company handle. (For example, after complaining that I couldn't find drivers for Windows 8.1 for my Samsung laptop, a Samsung customer service agent replied telling me how to use their update tool to download working Windows 8 drivers.)

Actually, they did. Verizon has just yet to deliver. Apparently they don't expect to deliver until the end of the year in any case.

Why are you using "Waterfox" and 64 bit nightlies? The official Firefox builds themselves have been 64 bit for several years now.

Assuming you're using Mac OS X or 64-bit Linux. It's just Windows that doesn't have a 64-bit Firefox for some dumb, poorly explained reason. (Keep in mind that 64-bit Firefox on Mac OS X managed to support 32-bit plugins, so it's not that. Clearly they can manage.)

Firefox already is 64-bit and has been for quite a while.

Just, not on Windows. I think their excuse was something to do with third party plugins not being 64-bit. (Although I'm pretty sure they have a 32-bit plugin shim that works on Linux and Mac OS X, so whatever.)

I don't really care, though, since Firefox 30 entirely broke Firefox with the proxy where I work. Now I can't access outside sites at all due to OCSP errors and I can't access internal sites since they removed NTLMv1 support as a "security hole."

But the fact that it hid it until someone finally tried it on a device is the simulator's fault.

And you've never had websites that did anything even somewhat complicated in JavaScript, huh? Since you aren't allowed to run interpreted code on iOS, it had to be redone in Objective-C, and the initial version turned out to be very slow. (Think "charting.")

I mean, sure, we could have just embedded a webpage and done it that way, but the existing JavaScript was already unacceptably slow or we wouldn't be looking at making an iOS app, now, would we?