That's fine for APIs that require registration. But I use the Calendar API. It doesn't require registration, and like many people I was caught out on the hop on November 17th when the v2 API was shut down. Like I said I'm not complaining. The v3 API is superior, but I would like to know if there is simple notification system available.

Not that I'm complaining, but you really do need to pay attention to Google's plans if you have any applications that make use of their APIs. They do love to cast things adrift on a pretty regular basis. Maybe I don't do enough development to pay the proper attention, but does Google have a single source for announcements like this? Perhaps an RSS feed would work, then I could use Google Reader to keep an eye on things. Oh, right.

Why is it that these major news outlets (Forbes, CNET, CNN, etc) all have articles about this new trojan/virus. They quote statistics from Symantec about the number of infect machines, and yet, not one describes how you can detect an infection. They must know. One previous post identifies a Symantec white paper describing the trojan's behavior (Here). Why don't these articles describe the steps required to detect it? It's not like they're under any obligation to encourage readers to buy into Symantec's bloated anti-virus products.

The Old Reader (http://theoldreader.com/) works pretty well for me. Not quite as sophisticated or instantly speedy as Google was, and it can take a few more minutes to be up-to-date, but free and you can import your feeds, which you had already exported from Google Reader, right?

I only looked at the Sudoku code, but writing a brute force puzzle solver in a procedural programming language hardly qualifies it as a suitable programming language for general puzzle solving.

Indestructible. The ultimate keyboard. Bought one as a spare 12 years ago, just in case. Still sitting in its box. The best!

Damn it!

And these are the companies that healthcare.gov (well at least the New York one) are using to validate customer's data. I'm surprised no one has brought this up yet.

I'm not fully knowledgeable about how carbon frames are finished, but assuming that an RFID could survive the process, I think this is an excellent idea.

A nice idea, but carbon frames don't have a stamp, or engraved serial number. It's usually a sticker, or similar, which is easily removed or painted over.

Utter, utter, utter ****s

Oh you big kidder you.

Scan all simple file details (name, size, date, path) into a simple database. Sort on size, remove unique sized files. Decide on your criteria for identifying duplicates, whether it's by name or CRC, and then proceed to identify the dupes. Keep logs and stats.

Yes. I when I still had that, AND a job.

As I used to say "it was damn difficult to write, it should be bloody difficult to understand".