EagerEyes Shorts

Musings on visualization, photography, programming, etc. that are too long for Twitter but too short for (or don't fit) my visualization website, EagerEyes.org. Part of my vanity website, kosara.net, which is most notable for hosting my list of publications. If you still want to know more, see my university page at UNC Charlotte, and/or follow me on Twitter.

Boxcar is very awesome. It pushes notifications about Twitter mentions and retweets, and using its simple API, I can have my server push messages to me (it can also push messages about other things, like emails that arrive). That’s even better than a twitter bot, because I don’t have to even have twitter open to get the message.

Being able to tap into the stream on other devices is a great idea, and will make it even more useful.

Affectionately nicknamed the ‘farm’, we’re pleased to introduce real time access to your own Boxcar notifications.

View the documentation here. We’ve created a sample Ruby implementation over on Github.

This is a technology preview for developers.

Posted at 8:13pm.

From Wired’s story on the guy who found and sold the 4G iPhone to Gizmodo, Brian Hogan. He seems to be blaming Gizmodo for leading him to believe that selling it (or “giving them access”) was okay. This is going to get pretty ugly if it goes to court – and it looks like it will.

Posted at 7:19pm and tagged with: apple, iphone,.

A friend of Hogan’s then offered to call Apple Care on Hogan’s behalf, according to Hogan’s lawyer. That apparently was the extent of Hogan’s efforts to return the phone.

This is an almost completely nonsensical “infographic” about Apple’s iPad. It’s a collection of random facts, many of them represented in the wrong way (see the pie chart on app prices, for example). It’s no wonder people are getting weary of the flood of infographics. Many of them are like this: good-looking but devoid of any content.

Shame on you, businessinsider.

In related news, see my posting on the Visualization Cargo Cult.

Posted at 9:24pm and tagged with: apple, ipad, infographic,.

This is an almost completely nonsensical “infographic” about Apple’s iPad. It’s a collection of random facts, many of them represented in the wrong way (see the pie chart on app prices, for example). It’s no wonder people are getting weary of the flood of infographics. Many of them are like this: good-looking but devoid of any content.

Shame on you, businessinsider.

In related news, see my posting on the Visualization Cargo Cult.

This image of the three-dimensional distribution of dark matter looks like it’s straight out of Star Trek: the Dark Matter is Condensing and About to Attack the Enterprise.

But apart from that, it’s actually not a great image. It uses the rainbow colormap, and it seems to only convey limited information. Is the distance really all that important? Do they have an image showing amount of mass, but it’s not as pretty? What about the data they used to calculate this, I bet that’s much more interesting than where on an image of the sky the dark matter can be found.

Posted at 11:01pm.

This image of the three-dimensional distribution of dark matter looks like it’s straight out of Star Trek: the Dark Matter is Condensing and About to Attack the Enterprise.

But apart from that, it’s actually not a great image. It uses the rainbow colormap, and it seems to only convey limited information. Is the distance really all that important? Do they have an image showing amount of mass, but it’s not as pretty? What about the data they used to calculate this, I bet that’s much more interesting than where on an image of the sky the dark matter can be found.

Neven Mrgan thinks the next iPhone might have the same screen resolution as the iPad:

Unless, of course, Apple comes out with an iPad-resolution iPhone

On a slightly larger screen that the current one, this would call for the crazy PPI of 341 (the current one is 163). The Droid, by the way, is 267, which I also would’ve called crazy a year or two ago.

I don’t know if a 340-PPI display is possible, affordable, or necessary. What I know is that it would let developers take their newly iPad-ified apps and move them to the iPad a bit easier; I don’t mean literally, since adjustments would still have to be made to account for the general form factor of the device. But it would be a little easier than developing for a completely different resolution.

It’s not going to happen, though, for three reasons:

  • Resolution. Even if the next iPhone was the same resolution as the iPad, that would not save developers much time. At the same pixel size, controls would be much, much smaller, so a different UI would still be necessary for the two devices. Apple has introduced a few new UI elements for the iPad, and it’s doubtful that many of them will be available on the iPhone. That is not a question of pixels, though, but a question of usability and fitting the UI to the device. Scaling iPhone design elements up may look clunky, but at least it’ll be usable. Scaling iPad stuff down will be unusable.

  • Form factor. The iPhone’s aspect ratio is 3:2, while the iPad is 4:3. This makes sense for the different devices because they are used in different ways. A phone that is mostly held in a portrait orientation needs to be longer so it can show more data and can show the keyboard plus a reasonable amount of text. The iPad is a very different beast that would look oddly long at that aspect ratio. Changing the resolution is one thing, but changing the aspect ratio is quite another. While I don’t doubt that we’ll see an increase in resolution (if not this year, then next), they’re not going to change the aspect ratio of the device.

  • Horsepower. All those pixels need to be filled with content. This is already an issue with the Nexus One, which feels slow because it can’t push all those pixels around fast enough. And its screen is still a far cry from 1024x768. The horsepower to drive that many pixels will not be feasible in a phone form factor (and power envelope to keep battery life acceptable) for years.

So while it is quite likely that we will see an increase in screen resolution in the next iPhone, it’s a safe bet to assume something closer to 480x720 or thereabouts, not something crazy like 1024x768.

Posted at 11:49pm.

Mike Wirth asked me to submit up to five pieces of work to an art/design show he was organizing, called MineShow. The idea was to get work that 12 Charlotte-area designers had done on their own, rather than for somebody else.

The show opened last night at Queens University in Charlotte, NC, and will be open until April 9, 2010.

Three of the pieces I submitted were accepted: the U.S. ZIPScribble Map, the iTunes 10 Billion Downloads Visualization, and a screenshot from the Parallel Sets program showing the Titanic dataset.

There was quite a bit of interest in the visualizations, particularly the ZIPScribble Map and the Parallel Sets. I had been a bit unsure how these visualizations would stack up next to the more artistic work, but they actually fit in quite well.

It was fascinating to watch people explain to each other what they were seeing. There were usually small groups of people there looking at the images together.

Of course, the other pieces were highly interesting too. They also tended to be framed much better than mine and usually quite a bit larger. I’m still learning. But it was a great experience, and I hope to have this opportunity again.

Posted at 9:00am and tagged with: two column,.

I was looking for Kaiser Fung’s Numbers Rule Your World on Amazon, and saw that there was no Kindle version. So I figured I’d check with the publisher, McGraw-Hill, if there was perhaps some other kind of e-book (like O’Reilly has for most of its titles).

Googling for the name McGraw-Hill took me to their Corporate Website, which has a convenient little search box in the upper right. So I typed in the title, but only got bogus results. Nothing seemed to match the full title, and the pages were all generic corporate-style stuff.

Turns out there’s a little drop-down box on that search results/refinement page where you can select what you want to search. It defaults to McGraw-Hill Corporate, but it has options like Books and Educational Products. And lo and behold, of course it finds the book once I tell it to search for books.

But why does it search the corporate site first? Isn’t it more likely that people will want to search for your products, rather than your press releases or investor info? You have a lot more customers than investors, so why does your search default to boring corporate stuff?

It’s not that there is an additional step involved here that I can’t be bothered with, it’s the attitude. I don’t care about your org chart or your subsidiaries or whatever. I want information, fast. I want the website that comes up when I search for your name to make sense to 90% of the people. How can you put so much effort into a website and not think about who the visitors are and what they’re looking for?

This is similar to HP’s “license plate” URLs, and I’ve seen IBM do the same (though they seem to have stopped doing it). Don’t tell me your internal structure or your server names. Don’t tell me what you think is important; I don’t care. I care about the stuff that’s important to me. I want a simple URL, I want relevant information.

Is that really too much to ask?

Posted at 10:05pm.

These scans from the Ninth U.S. Census 1870 are truly fascinating. Check out the fiscal chart on page 35, the population pyramids on pages 40 and 41, the death charts on pages 45-46, and the disabilities on pages 49ff (including “insanity” and “idiocy”). There are also a few more treemap-like pages like the one above.

Incredible to think that all of these were done long before computers, by hand. The number crunching alone must have been a huge task, and then drawing these charts and transferring them onto plates for printing. Wow.

(via robertogreco)

Posted at 10:09am.

These scans from the Ninth U.S. Census 1870 are truly fascinating. Check out the fiscal chart on page 35, the population pyramids on pages 40 and 41, the death charts on pages 45-46, and the disabilities on pages 49ff (including “insanity” and “idiocy”). There are also a few more treemap-like pages like the one above.

Incredible to think that all of these were done long before computers, by hand. The number crunching alone must have been a huge task, and then drawing these charts and transferring them onto plates for printing. Wow.

(via robertogreco)

fuckyeahinfo:

datavis:

Why does a salad cost mmore than a Big Mac?

It’s a good cause, but the chart badly distorts the data. See my recent March Chart Madness criticism roundup for an explanation (it’s about 2/3 down the page).

Posted at 11:24am and tagged with: visualization, distortion, criticism,.

fuckyeahinfo:

datavis:

Why does a salad cost mmore than a Big Mac?


It’s a good cause, but the chart badly distorts the data. See my recent March Chart Madness criticism roundup for an explanation (it’s about 2/3 down the page).

Interesting idea by Sam Loman: the human body as a subway map. Blood vessels, nerves, digestive system, etc.

Posted at 8:25am.

Interesting idea by Sam Loman: the human body as a subway map. Blood vessels, nerves, digestive system, etc.