Really, dude? Really?

Wow, that segway was about as awkward as some kind of two-parallel-wheeled auto-balancing minute-muscle-movement-controlled vehicle. Of some sort.

Everyone's putting words in my mouth. Of course it's scary, I don't agree with it, I was just answering the question how one thing could be illegal but another thing wasn't. The DMCA is an affront to free speech and fair use.

Oh certainly, no argument there. I didn't say this guy could use the fair use defense, I was just saying that the DMCA itself, on paper, shuts down a lot of fair-use avenues.

Good point, modern cars do have DRM-protected ECUs. My old Grand National had no such protection though :)

I was more responding to modifying for reason xyz vs. modifying for reason of circumventing copyright measure, and why modifying the consoles was different from making a general modification to a car, even one that might lead to you breaking other laws (like speeding.)

It's illegal because the law, in this case the DMCA (http://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act) specifically criminalizes the circumvention of a copyright measure. Sure this flies in the face of hypothetical fair use, for example, making backups of original games to protect the originals from damage. But he intentionally modified hardware put in place to enforce copyright, and therefore broke the law.

Modifying a car doesn't run afoul of the DMCA. The car is still legal to own and drive, is usable on the road if kept inside the legal speed limit and passes whatever vehicle inspections your local municipality imposes, and is usable on closed tracks and in legal racing situations and the like. Modifying a console so that it no longer handshakes with content to ensure the media is the original factory media; circumventing the console's ability to control access to copyrighted works (to quote the DMCA) breaks the law.

That's pretty funny, I used to hate on WD as well, until last month when we upgraded all the drives in our SAN to 1.5TB drives and pulled all 18 old WD 250GB drives. In three years, with about a grand total of 40min powered-off time, with constant reads and writes through nights, weekends and holidays, none failed.

Not exactly a real-world scenario relevant to desktop use or even a file server, but I thought it was interesting.

Many iPhone "2G"/first gen. hardware contracts are more than the approximately (maybe it's exactly?) 18 months it takes for your contract to be upgrade-eligible. The issue here is more the people who bought the iPhone first gen very late in it's life cycle, or bought into the 3G at all (since it's only been available for about 11 months.)

Seems people just feel confused and betrayed by Apple, because those who purchased iPhone 3G phones (myself included) adopted early, and also were first gen. customers as well. Many of the people in my situation feel screwed that they have to pay an upgrade fee while new adopters get in on the iPhone 3G-S goodness for free while we've been loyal customers all along. That said, I realize it doesn't really work that way.

I understand how subsidies work, and I realized that the iPhone 3G was released approximately 1 year after the iPhone "2G"/first gen., but maybe if I knew the iPhone would be updated again after only a year, I might not have purchased the iPhone 3G. Nevertheless, the iPhone 3G does suit my needs completely and will continue to do so until approximately January 2010 when I can upgrade to the iPhone 3G-S, or at that point, I could also just wait and see if the iPhone 4th gen is coming down the line at the one-year mark just like this one. And if so, I'll evaluate then if it's worth the additional 5 month wait.

I'm smack in the middle of the Philly metro area, and apparently, AT&T isn't offering coverage enough to suit the features of this phone to me either. Or NYC metro. Or anywhere in America, for that matter, at least for a while. MMS and tethering have been around for years and years, but one won't be ready at launch, and the other was totally glanced over and for now appears delayed without mention of availability time-frame.

I've never seen the rules one should follow when releasing a device that might end up in millions of hands, but I'm sure they include the following:

1) Don't use an unstable hack to enable a feature that a very large percentage of potential users will be counting on.
2) Don't base a feature on a cat-and-mouse game. Especially with the likes of Apple, who are really good at that particular game.
3) Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup. Jobs was bragging about patents in the iPhone announcement keynote, for Christ sake.

All that switching from RISC/PPC to x86_xx should change is "endianness." I hear passing worries of Intel chip-level vulnerabilities, but to my (admittedly limited to hitting up Google just now) knowledge is that these never really end up in mainstream exploits. Maybe, because there are plenty of much more easily exploitable vulnerabilities already known.

Again, not a security researcher or a system arch. expert myself, but what I've heard from those researching OS X vs. Windows vulnerabilities, Address Space Layout Randomization (ASLR) would make it much harder to exploit vulnerabilities on the Apple end. This feature appears to be slated for the next point release ("Snow Leopard") of Mac OS X. Essentially, the exploiter must try much harder to "find" the code planted in the target box's memory, when the vulnerability was exploited, in order to execute it.

It's so that when things happen, like a worm infection for example, they don't have to have a custom anti virus solution to take care of it. They can just use off the shelf Norton AV to clean up infections. Why spend precious tax dollars on a custom system when off the shelf stuff works even better?

And to me, it makes perfect sense to connect them to the internet, so that they can receive all the virus def. updates and WIndows patches as fast as possible.

Not to start a flame war or a vocal-minority thing here, but am I alone in having virtually no issues at all with iPhone's ActiveSync capability? I've been using it for work email since day one and haven't had a single issue. What issues have you had?

Okay, both of those flaws you cite require user interaction. That doesn't constitute a "virus" or a "worm." That's a vulnerability. A vulnerability, I might add, never amounted to anything in the wild, and was patched quickly by Apple. Not an apologist, flaws are flaws are flaws. But they aren't viruses. The distinction is important.

That would be called a "flash," and it would be a "feature." :) I'd be perfectly fine with it.