wonderercat

What amazes me is how Microsoft consistently explains design with obviously aliased images using nasty, bandy palettes.

I hope the explanation is that their web publishing framework just sucks and has no oversight, because it would be troubling if the designers/bloggers missed this.

> Create a problem.

> Sell a solution to that problem.

Force everyone in the country, by law, to buy the solution.

I'm not even talking about the latest TSA BS; are we all forgetting that our taxes -- our money -- has been literally purchasing the TSA's nonsense from the very beginning?

...which is easily defeated by a regex, no?

I'm doing a (tangentially related) twist on this sort of thing, so I'll ask you the questions that haunted me for months until I could answer them about my own project:

Who's going to use this?

I mean, what's the intersection of people that are computer-articulate enough to know what to ask for ("convert this file for me"), but don't know how to do it, and/or are willing to spend the extra minute or two to post and manage the "favor"? Especially when "know how to do it" means "google for the free web app that does it"?

And who is going to spend their time doing these favors, with no reward except some ethereal concept of "points" that can only be redeemed for doing the things I can already easily do myself (see above)? Realize that you're competing for attention from facebook/twitter/HN. And MTurk, which actually pays.

You could still use bcrypt and do the comparison work server-side.

Depending on work factors and whatnot, it's now a backend load balancing issue. But it's probably solvable.

I suspect they are matching bits.

Though since this is going through hashing, the number of matching bits has (by design) zero correlation to how close the P/W is. In which case, yeah, I think the binary indicator would be more useful and intuitive.

> My guess is the machines could be modified to change the background color behind the scanned person's silhouette.

For a billion dollars, I would have demanded, at minimum, that modifications to make the machines actually work be included. That they weren't just underscores the idiocy at play.

> The quote from the TSA ("Any guidance provided is to caution reporters not to generalize...") is merely saying "don't jump to conclusions on the basis of some activist's blog post/video," which is quite a reasonable "cautionary" statement.

It would be reasonable, if this were a citizen petitioning the media. Except this is the government, funded by the people, telling the media on their behalf what should and should not be discussed. The most charitable analysis is that my hard-earned tax dollars are being flushed on unsolicited media curation. A less charitable (and I believe, more likely) explanation is an attempt to sidestep the first amendment with no repercussions because it's not censorship, just chilling effects which nobody can be held accountable for.

So at best, complete incompetence, and at worst, conspiracy. Either way, I think the outrage is justified.

About as much of a stretch as using a unicorn for "delete", because unicorns don't exist.

I'm getting increasingly concerned that web UIs are trading away usability for design in Apple's wake, forgetting the part about "design is how it works".

I think it's interesting that the #1 feature on their features page is labeled "Always up. Always on."

And unfortunately that with outages like this, that number's probably not increasing anytime soon.

Once again you're demonstrating that you really don't know how to use Mercurial, but feel the need to bash its usability anyway.

   hg update <branchname>

will do exactly what you want. It's even the same command as in SVN.

> There are a number of publishers on this list, including my own publisher. If the consensus I get from readers is that we should boycott publishers, I'll support the boycott even though it hurts me.

As much of an asshole as he is, I've always respected the guy for his shocking lack of hypocrisy.

If movie producers had the decency to make this kind of public stand, things might be different.

Most likely because of things like

  @-webkit-keyframes gameover{

Indeed. I had to audit the source believe it, but this is actually legitimate.

Massive abuse of data url's and keyframes, but it works.