444 karma · joined April 25, 2011
When an error is encountered it makes all the diffence that it was on a machine running ie7 (as an example).
What info do you report back? What format is it? Do you handle different types of errors? And if so how do you report them? Do you plan on providing an API for devs to retrieve this info?
That's all I can think of on the spot, I just think you know your product better than anyone else, adn if you were trying to convince yourself to use it, surely the 8 point feature list wouldn't cut it.
While I understand that you don't want to over complicate the features section, the reality is that the people you're targeting should have more than a basic understanding of whats happening, and you should talk to them as such. - Unless you're targeting managers and hoping they will force this on their developers.
Edit: I notice you have _some_ technical info in the FAQ, but my personal opinion is that if you're targeting devs you need MOAR.
tl;dr: Give us more info.
Edit: just noticed comments below about licencing of N_de etc etc, so I assume this is the reason
Edit: I'd be interested in helping/contributing.
I'm not sure whether this is due to my profile not being indexed or that its rank is so low so as to be negligible.
Would be nice if they explained their ranking system better. (On the site itself)
I was disapointed.
Still nice despite the catch22 though.
One this that got me though, in terms of usablity, is that me being at GMT+0 it was hard to determine if the far right of the graph was current or lagging?
but I'll definitely be checking this out in the future for launch planning etc.
I reccomend everyone reading Hacker News that _happens_ to be involved in the web industry should fill this out, to create a broader picture.
[1]: in the loose sense of the word.