I think you're skewing the numbers a bit to support your conclusion.
4% have 24", 5% have >24". That _doesn't_ mean 9% have 1920x1200 or more. TVs have many inches but not that many pixels. Also, not all 24" is 1920x1200. 1920x1080 24.1" monitors may be entered as 24", but would show up in the 1.39% 'other' resolutions. Number of inches is probably user specified too, so there is probably some errors in the data.
Skewing the numbers the other way, the 5% are TV owners and 3.68% (2.29+1.39) have 24"-resolution (1920xsome or other). That leaves a difference of 0.32%, which are those that entered the data wrongly.
So I wouldn't say the numbers are bullshit and WAY out of wack, but I'll agree there is some weirdness. It would have been nice to have access to the raw data. Then you could answer questions like 'What resolutions did those that said 24" report?'.
Still, inaccuracies and all, it's an interesting list.
Amazing... Some people don't read the stories or the other posts. THE PROTOCOL IS CALLED SECSH. NOT SHH.
Okay? Got it? SSH is an implementation of SecSH. OpenSSH is an implementation of SecSH. Clearly, OpenSSH is leaching off the brand and name that SSH has developed. Renaming it, as they are doing to OpenSecSH, solves all these problems, and the guy is happy with that.
Well, according to the IETF, it's called both. secsh in the headers, but SSH almost everywhere else. See http://www.ietf.org/html.charters/secsh-charter.ht ml Most of the documents on this page are from January 2001, and it's SSH this and SSH that.
T. Ylonen is one of the authors of these. Calling it the SSH protocol should be ok, when even the author does it?
Well, checking the JavaScript docs, it seems getYear returns two-digit year for 1900-1999, and four-digit year for others. So the code _is_ y2k compatible. For JavaScript 1.3+, one should use getFullYear instead.
Slashdot Mirror
I think you're skewing the numbers a bit to support your conclusion.
4% have 24", 5% have >24". That _doesn't_ mean 9% have 1920x1200 or more. TVs have many inches but not that many pixels. Also, not all 24" is 1920x1200. 1920x1080 24.1" monitors may be entered as 24", but would show up in the 1.39% 'other' resolutions. Number of inches is probably user specified too, so there is probably some errors in the data.
Skewing the numbers the other way, the 5% are TV owners and 3.68% (2.29+1.39) have 24"-resolution (1920xsome or other). That leaves a difference of 0.32%, which are those that entered the data wrongly.
So I wouldn't say the numbers are bullshit and WAY out of wack, but I'll agree there is some weirdness. It would have been nice to have access to the raw data. Then you could answer questions like 'What resolutions did those that said 24" report?'.
Still, inaccuracies and all, it's an interesting list.
Put a 10Mpbs hub between the printer and the network. Free rate-limiting.
Or would that still be too fast?
Well, according to the IETF, it's called both. secsh in the headers, but SSH almost everywhere else. See http://www.ietf.org/html.charters/secsh-charter.h
T. Ylonen is one of the authors of these. Calling it the SSH protocol should be ok, when even the author does it?
Well, checking the JavaScript docs, it seems getYear returns two-digit year for 1900-1999, and four-digit year for others. So the code _is_ y2k compatible. For JavaScript 1.3+, one should use getFullYear instead.