Also, with the Pre "spoofing" the Apple ID to work with iTunes, what I was trying to say is that Apple shouldn't be allowed to make that a requirement for iTunes. Sure they can at this point, but again they aren't the underdogs in this area anymore. They can get away with that sort of thing with computers because their competitors are so huge, but that's not the case with Apple's other products.
I think I must be misunderstanding you. Are you actually saying Apple shouldn't be allowed to check what the hardware is before trying to sync to it?
If that actually *is* what you mean, then iTunes would be forced to try syncing music/videos/etc to *every* USB device plugged into the computer (printers, scanners, thumb drives, cameras, speakers, etc.)
The idea behind those USB IDs is that they are supposed to enable the computer (and software on it) to uniquely identify any particular type of device. If Apple shouldn't be allowed to use those IDs for their intended purpose, how would you recommend they distinguish an iPod from a USB microphone?
Apple is intentionally blocking the Pre's (and now Pixi's) ability to pretend to be an iPod because doing otherwise opens them up to much more painful risks in the future. If Apple were to simply allow it, here's a few scenarios that would happen.
Scenario 1) Apple silently allows the Pre to sync with iTunes by pretending to be an iPod. Apple makes a change to the protocol (say encrypting it to allow syncing across the internet). Suddenly, the Palm devices that worked for years stop working. Apple can't send an update out for the Pre, and since Palm didn't actually license the syncing protocol, they have no access to the new encryption keys. Apple gets a real black eye on this one because they've 'supported' syncing to a Pre for years. Users sue because *Apple* has disabled some functionality.
Scenario 2) Apple silently allows the Pre to sync with iTunes by pretending to be an iPod. Palm makes a change to the Pre's firmware, and in a small percentage of cases this change causes iTunes to trigger a glitch which bricks the Pre. Again, Apple gets the bad press, because plenty of *other* users aren't having any problems with their Pre, so it must be *Apple's* fault.
Scenario 3) Apple does its best to actually support syncing with the Pre with the iPod sync protocol. Then one day Apple updates iTunes the same day Palm pushes a firmware/OS update to the Pre. Users who update one but not the other have no problems, but users who update *both* run into an issue where a small number have their Pre irrevocably bricked during the sync. Who should the users be upset with?
Apple is actually unable to *support* syncing with the Pre, because they can't control what the software on the Pre does or how it behaves. If Palm wants their users to be able to use iTunes as their media library, they should go the route RIM (and several other phone manufacturers) went, and create a utility that uses one of the documented *and supported* interfaces Apple provides to allow 3rd parties to interact with iTunes. Instead, they decided to pass the support responsibility off onto Apple.
If Apple needs to change the sync protocol for iPods in order to enable new functionality, but they aren't allowed to break syncing with the Pre, you've just created a constraint where Palm is allowed to restrict Apple from providing new.
Palm advertises functionality which is not, and never was, within its ability to guarantee, but somehow this is Apple's fault? How?