I agree with much of your comment, but I am a mite frustrated with the assumed gender differences. Granted, there are populations of male nerds who have less than stellar reputations for good reason, but nerd arrogance isn't an exclusively male tendency. I've seen it in women, and as a female nerd I hereby assert and confess that I had more than my share of nerd arrogance once upon a time, especially as a computer science undergraduate. Even now I think back on the abusive ways I communicated and the walls I inadvertently put up that blocked genuine collaboration and collegiality, and I wince. 12 years later, I've worked long and hard on cultivating compassion and humility in my personality and have seen incalculably valuable return on that investment.
There may well be a positive correlation between nerd arrogance and what emerges as "male" from socialized (and unfortunately binary) gender differences, but in my opinion there is utterly insufficient data to confirm that statistically, so I'd prefer to stick with the "attitude of arrogance and superiority among nerds" as the question at hand instead of speculating about the gender correlation. In fact, your own anecdote undercuts your speculation by explicitly attributing the difference between computer science and jazz to the nature of the field instead of the gender ratio:
Jazz Majors were predominantly male too. However, due to the nature of Jazz where the band works as a team, there is less arrogance
The reason I say that there is insufficient data to confidently correlate gender and nerd arrogance is that there are simply too few women in the field, and given the nature of the field, those women who do enter it have already gone through an element of pre-selection. (Note: so have the men in the field.) If the population were considerably more diverse and if the field didn't have an earned reputation as having gender accessibility issues, then I would consider speculating about gender. Until then, it makes more sense to leave it to personality and socialized behaviour.
What do you think?
Despite fully intending to for several years, I haven't actually sat down and devised a coherent plan for key management including an authoritative physical store for the private keys (a problem because in any given day I use 4+ computers and not one of them accesses my email directly), revocation certificates, choosing a reliable keyserver, and choosing a web-based way to distribute my public key to anyone so inclined.
To make matters worse, I'm still in a state of severe digital identity flux (SDIF henceforth). I've been in SDIF for a number of years, and the problem is compounded by the fact that all the commonly used and centralized "identity authorities" (self-styled) are corporate and make me acutely uncomfortable. Until I resolve SDIF and establish the requisite collection of identities, boundaries to each, and reputations, I feel as though what digital assets I have aren't worth the trouble, especially if it's going to be temporary. I don't want to go to all the trouble of planning things (as per paragraph #1) only to then have to revoke and re-issue everything.
Slashdot has been a significant part of the formation of my identity in terms of interest, exploring diverse issues, and exposure to technologies that I wouldn't otherwise have encountered. I thank you, Rob, for everything you've done to create and cultivate this community.
I've been thinking more about Slashdot recently because of my involvement in "Nym-Wars". In at least one place Slashdot was cited as a stellar example of the civility and quality that can be fostered in a community that functions primarily pseudonymously, but also allows anonymity (two things I very much are about). The moderation system in place here is complex (I myself still find it a little confusing) but there is no question that it works. Slashdot is one of the few places where I consider the comments on an article as much (often more) worth reading as the article itself. Obviously my appreciation for this applies to the whole Slashdot community, but I am posting this specifically in recognition of CmdrTaco's influence in shaping the community.
Rob, may everything else you do in the years to come be as interesting and fruitful as your work here! Community and communication are essential, amazing things, and I'm sure your contributions to the world at large are far from over.
or just use 22.214.171.124 and 126.96.36.199.. or 188.8.131.52 and 184.108.40.206.
it's not necessarily the regexp comparisons, but that DOM manipulation is pretty slow in Firefox.
a lot of the time this can point to patent issues
So what you're saying is that the US patent system is anti-competitive and harmful to consumers?
so if you spend millions/billions developing a microchip, then sell a phone that uses it..
you'd be okay if I just opened up the first phone that rolled off the assembly line and duplicated your chip? then started selling clones for a tenth of what you charge?
that's what happens when there's no [reasonable] patent protection for hardware. see: China.
The cheap tablets and handhelds that you can buy everywhere else in the world just aren't in the US. It seems fishy.
a lot of the time this can point to patent issues. there might be chipsets (often the radios or something else fairly narrow) that prevent legitimate US import.
I'm having trouble finding it now, but sometime in the last few years there was a pretty major seizure by Customs in a situation like this. I believe it was related to this, if memory serves.
Why this is being given such legal scrutiny. Its akin to driving down the street with a tape recorder and parabolic mic, recording whatever conversations people might be having as part of a population density study, and accidentally recording someone in their front yard yelling their cc# into the phone. It should fall under general privacy law: if you dont spend the time/energy to setup encryption of some form, dont expect privacy (same as if you dont try to block peeping toms, or if you go sunbathing nude in your front yard next to the street, dont be surprised to find yourself posted to
What if I sniff all the guests' network traffic in a hotel? (via ARP spoofing or otherwise)
There's certainly no warnings presented in any OS when you plug in ethernet and grab an IP, and the average computer user certainly doesn't know that it's possible to do this.. so, how do you feel about that?
When Microsoft's Kin was released a month ago, it came with the usual sequence of tittilating leaks (project Pink), a swell of coverage leading to liveblogging of the release press conference, and an advertising blitz impressive in its scope. Since it's supposed to be a social phone of course it has numerous fansites including Facebook and Twitter. Of course there's a Wikipe
An unmodified, unrestricted Android OS phone would be a selling point in and of itself.
There is, http://en.wikipedia.org/wiki/Android_Dev_Phone - you can buy it directly from Google. Sign up as an Android developer for $25 (one-time fee that gets you access to submit apps for the Market, required to purchase the phone unfortunately). The latest version of the phone is actually just a completely unlocked HTC Magic; it costs $399 from Google (no contract subsidy here obviously.)
If you're interested in a "solution" (only workable to tech savvy folk, really) for from-carrier devices you can pick up any Android device you'd like, root it (attain su via exploits, there are one-click scripts for every popular device) and install whatever OS version you'd like on it. XDA-Developers forum has hundreds of custom Android "ROMs" that have been developed by regular users with no more access than the phone they bought and the Android SDK.
You can install a regular 'vanilla' release of Android OS from source and customize (or not customize) to your heart's content.
maybe a better practice would be to store a thumbnail size image of the screenshot.
They _are_ only storing a thumbnail; the article just sucks.
# ls -l | wc -l
# du -h .
Here, I uploaded the largest one out of the 62 for your review.
Life would be so much easier if we could just look at the source code. -- Dave Olson