I can see one way in which this might be both true and proper. If each account was individually encrypted with keys that only the users had, what they're saying would be completely true. And I think it would be completely proper and even laudatory to run an email system that way. They could search individual accounts by having the users decrypt them, but they couldn't do a wholesale search of the entire email system. This is the way email should be!

A somewhat more likely approach would be that by policy, users are not allowed to keep email on the server. All email must be downloaded or deleted. No online folders, ridiculously small INBOX quotas, maybe a read-once policy where as soon as the mail is retrieved the server auto-deletes it. I can actually understand this being done; I've worked with corporate lawyers who would love to have the email system set up this way for the express purpose of defeating global searches. Anything can be twisted and used against you, so save nothing, leave no evidence. I certainly don't agree with that mindset, but I've worked with people who are like that.

Not that I think it actually is done either of those ways. I think it's far more likely that they're simply lying and refusing to comply. It's probably simply policy to refuse such blanket FOIA requests, and there's undoubtedly a clause buried in the FOIA itself that allows them to require that requests be specific and narrow. You know, in the way that searches of private individuals are supposed to be.

Binary vs. text doesn't make any real difference for debugging. Ethernet frames are binary, IP is binary, TCP is binary. We cope just fine. It may be more difficult to do a quick-and-dirty "echo 'GET / HTTP/2.0' | nc localhost 80", but so what? You can still use HTTP/1.1 or even HTTP/1.0 for that, and you're going to haul out the packet analyzer for any serious debugging anyway.

What I really don't like is that they're multiplexing data over a single TCP connection. I understand why they're doing it, but it seems like re-inventing the wheel. Congestion control is tricky to get right so I see HTTP/2.1 and HTTP/2.2 coming out hot on the heels of HTTP/2.0 as they iron out problems that have already been solved elsewhere.

A driver that shouldn't be on the road can kill you.

That applies to any bad driver, regardless of if you're even riding with them. It's not an argument either way for whether or not taxis should be regulated differently from other private vehicles.

Damn, that sounds like a perfect description of *my* 20 year-old son! I know exactly what you're talking about. We think he's capable of living on his own, but we're afraid to just plain give him the boot because there's that niggling little doubt that maybe he's really not...

We're trying a halfway situation right now. We got him an apartment and we're paying for basic necessities: rent, utilities, and enough money to avoid starvation but not enough (as he found out last month!) to eat take-out. He has to get a job if he wants anything more, like TV or internet. The apartment is 500 miles from home so there's no way we can just pop in to take care of problems for him. The location (Houghton, MI) was chosen for a bunch of reasons, but primarily because it's a small town, we know it well, and we have friends there he can call on if something does go seriously pear-shaped.

He's been there three months, and we're going to give it a full year before deciding what to do next. Houghton has really tough winters, so I'm hoping that if nothing else he'll decide that he wants to live anywhere *but* there and will be willing to find a job back down here (or wherever) in order to escape.

Anyway, good luck with your son!

Those are all reasons that the free market can take care of. Getting crappy taxi service? Cars are dirty, drivers are late and reckless? Switch companies. The good ones flourish, the bad ones die out.

So why should taxis be a regulated service? What issues can't the free market solve? The number of taxis allowed can be limited by the city to aid with congestion and traffic planning. Special "taxi only" lanes or parking areas can be designated without worry that every driver will simply declare themselves a "freelance taxi" and use taxi areas. Cities can require that taxi companies send a certain percentage of their cars to service undesirable neighborhoods, rather than letting every driver camp out at the plum positions.

I do believe that for the most part taxi unions are about protectionism, but there are some legitimate (that is, for the greater good of the population as a whole) reasons why cities would want a heavily regulated taxi industry rather than a more laissez-faire solution.

It decodes to "All your base are belong to us."

It seems to work well enough for the purposes, and avoids the XBMC issue of needing a general purpose computing device in the living room.

And what's wrong with having a general-purpose computing device in the living room? I run XBMC on a little Atom-based PC dedicated to that purpose. It's about the size of a hard-back book, draws very little power, and is silent. It uses a little wireless keyboard that's about the size of a game controller, so it's not like I have keyboard and mouse cables stretching across the room. For me it's the ideal set-top box.

Example: which way do you iterate through an array to apply an operation to each element? Well, _if_ you happen to have iterated through it recently, doing it backwards might be lot faster then doing it forwards due to cache locality. I'd love to see a compiler managing to take advantage of that.

I'd trust the compiler to do it a whole lot more than I'd trust the programmer. Things like cache locality are going to be very dependent on machine architecture. You should not be optimizing for machine architecture on anything that's intended to be the least bit portable. Yeah, you made it faster on your machine, but what about your user's? Will it have the same cache size? The same line size? Hell, will it even have the same word size and endedness? To the extent that any of this should be optimized, it's the compiler's job to do it.

Be sure to pick your algorithms carefully. Know the complexity, and don't choose an O(n^2) algorithm when there's an equivalent one that's O(n). But optimizing hardware-level stuff? Unless you get to pick the hardware, don't do it. Every optimization you make on your machine is likely to be a pessimization on someone else's. The compiler knows the architecture it's compiling for (well, usually...) and is in a much better position to make such performance decisions.

They don't check the accuracy of the factoid. They're just attaching a timestamp and their digital signature to whatever factoid you give them. You can later use this to prove that the factoid was a particular byte string at a particular time. (Though I'm not sure the level of "proof" this is, unless they're willing to appear in court and testify that the timestamp is accurate.)

The language on their website is very misleading.

Bah, where's the "delete post" button? I completely misread the parent post and posted exactly the same observation. I'm a dumb-ass.

I'd love to see an interstellar probe launched, but that is far beyond our current technology. We just can't do it.

Technically, we already have. But yeah, unless we count on it coming back as V'Ger in a couple centuries, we're not going to get a lot of interstellar data back from it.

Male or female, makes no difference. Women's magazines sell with pictures of women. Men's magazines sell with pictures of women.

Actually, that's not the case in general. Look in the grocery store check-out lane, or on the magazine rack. Yes, the men's magazines predominantly feature pictures of sexy women. But the women's magazines predominantly feature pictures of... sexy women. I'm sure it makes some relevant point in the discussion of sexism, but I'm not exactly sure what that point is.

So, what's stopping you? I hear a hell of a lot of bitching about how Google Reader is going away and how all the replacements suck. So what's stopping you (or anyone else) from tapping this vast, unserved market? It's not like parsing a bunch of XML files and presenting them in an organized fashion is exactly rocket science. Sounds like Google's opening up a golden opportunity for someone.

So let's assume he's being truthful and he actually has "source code for older titles plus development kits for the PS4 and Xbox One consoles". Um... So what? How is that damaging to the companies involved? Source code for older titles? Who cares? Dev kits? They hand those things out like candy to development studios. Sure, under NDA, but it's not like their business plan is toast if the dev kit gets leaked.

It sounds like a small price to pay to pick off and make an example of some pissant little self-proclaimed l33t h4x0r. With blackmail that weak I'd nail him to the wall just because he sounds like a prick.

When the TSA finds that pat downs are not effective at forcing people into the scanners they'll let us walk through a metal detector and leave us alone.

More likely, they'll continue to make the pat-down more degrading, invasive, and time consuming to ensure that people go through the machines. Yes sir, you absolutely have the right to not be x-rayed. Just step into that queue over there for the full strip-search. You do have your regulation 3 ounces of vaseline, yes? Current wait time is just under three hours, hope your flight doesn't leave before then. Have a nice day.

Or they'll just say to hell with the pretense and pass a law out-and-out requiring the use of the machines.