You might think that, but I just discovered that the 5-year-old software that I am working on was converting times from UTC by getting the current offset from UTC. No consideration was made for the actual date being converted. The people who wrote this weren't stupid, they just didn't really think through the problem. That, and the company had no culture of code reviews or even documented designs. The times, they are a changing.

Seriously, though, getting the current time is easy. Converting an arbitrary datetime for an arbitrary location involves a bit of thought. This is especially true when you have to deal with Arizona. And, that is without having to consider the conversion of historical data that occurred during different DST rules.

Even digital data uses a carrier wave.

The problem with this idea is that the human brain does not react well to large amounts of negative data. Eventually, the mental "squelch" of the viewer will drop to the point where they will see a pattern whether one exists or not.

I could see sending flagged data to humans, but this project is in "real-time". I think this is just a publicity gimmick.

I once had a game on my Mac called "Victory at Sea" (pre-OSX days). The game was buggy as hell, but the game was researched by Jim Dunnigan and Albert Nofi. They created a book of the same name from the research they had assembled.

Great research, crappy game (because it was unplayable).

Ahhh, Usenet...

I remember when someone spammed ads in the groups. There was a huge uproar over the notion that someone would attempt to use the Internet for commercial purposes.