iPhone Lawsuit Seeks Over $1 Billion in Damages
#2
Posted 12 October 2007 - 07:50 AM
#5
Posted 12 October 2007 - 01:29 PM
#8
Posted 22 October 2007 - 10:11 AM
#9
Posted 22 October 2007 - 10:48 AM
They admitted they knew that the contract signed at the time of the purchase precluded them using it for "extended" roaming and were at risk of having their service terminated, but they just had to have the phone. Yes, STUPID IS AS STUPID DOES.
If the standard contract in NE states the phone can only be used on AT&T networks, you can bet the ones in California do too. But then this is typical of California, sign the contract, ignore it, and then sue or cry on TV when it doesn't work out the way you want.
And anyone who had ever known anything about Apple, knows that only approved apps with work on Apple. It was true when the Apple II was released to the market, and it is true today - one of the reasons I don't have any Apple products, despite their hype.
This case should be thrown out, and the two parties originating the suit should be charged for the Court time wasted, but then there is a reason they filed it in San Francisco, a community not known for common sense. SF has a nickname on the truckers channel I won't repeat here, but LA's is "Shakytown"
#10
Posted 22 October 2007 - 11:30 AM
rgreen4 said:
Ummmm...not true if you where inferring that such a policy exists for Macs. There a LOTS of programs that run on Macs that are not "approved" by Apple. In fact, to my knowledge, Apple does NOT run a "certified for Mac OS X" program like Micro$oft has for Windoze.
Now, Apple has taken a much harder approach with the iPhone, which I frankly think is stupid...and is part of the reason why they are finally backing down and supposedly releasing a SDK kit for the iPhone soon. Thus, they will have an "officially" sanctioned way to use third party apps on the iPhone soon.
Now, as to the item at hand, at face value, many of these iPhone lawsuits seem stupid. As pointed out, many of these items where KNOWN issues that people could easily have known about prior to purchasing the iPhone. Thus, it would appear that such lawsuits should potentially be merit-less. I will note, however, that I personally don't know with precise detail all the details of the lawsuit...and as such, there maybe something of merit in them (and the news article is a little short on the details). The one definitely interesting part of the article was the claim in the lawsuit that Apple intentionally wrote the iPhone update to cripple iPhones that had been hacked/modified. If so, then they might have merit (I believe that there are provisions in the DCMA law that specifically allow such "unlocking" of cell phones and at least by implication might make it a "no-no" for a company to interfere with someone's ability to do such unlocking...i.e. iBricking someone's iPhone might not be permitted)...but it will be interesting to see if they can PROVE that claim.
#11
Posted 22 October 2007 - 12:56 PM
I also have a hard time feeling sorry for the owners of the bricked phones, since they knew that unlocking their iPhone was an unsupported hack. Unsupported hacks are often broken by future updates to the hacked code. If losing use of their phones was too great a risk, they shouldn't have hacked them. Don't gamble if you can't afford to lose.
On the other hand, after reading the iPhone warranty a few times, I can find nothing in it that states the warranty is voided by installation of unauthorized software unless the hardware is damaged as result of that software. Firmware is not hardware. Just about every state in the US has legislation that effectively creates an implied warranty that if a company sells a product, the customer has a reasonable expectation that that product work as advertised. Warranties implied by law always trump manufacturers' warranty limitations and restrictions. Apple may not have a responsibility to make sure US customers can unlock their iPhones for other carriers, but they do have a legal responsibility to make sure that iPhones (without hardware damage) will work on an AT&T network.
From what I have read, while there was only minor functionality change with the update, the underlying code underwent significant change. I think Apple has planned all along to release an SDK for the iPhone, but they wanted to wait until they had worked some bugs out of the code first. This was the first version of Apple's first phone. I don't believe Jobs or Apple were so naive as to believe the code would be bug free. Remember Cheetah? I also believe Apple would be more than happy to let users use the iPhone on other networks, but breaking into the telecommunications market required them to partner with an existing telecom company. As that partner, it is AT&T who is standing in the way of using the iPhone with other carriers. I seriously doubt the monthly payments Apple receives from AT&T are worth more than the lost market share of people who would buy iPhones if they could use a carrier other than AT&T.
#12
Posted 22 October 2007 - 01:18 PM
Talk about FUD! Anyone who knows anything about Apple knows that your statement is not true. Considering Automator, AppleScript, four different *nix shells, and Xcode Tools all ship with every new Mac (starting Friday a few more developer tools will be added to the package), I don't think one can claim with any kind of accuracy that Apple only allows approved apps to run on Apple products. If anything, Apple encourages third party application development.
#13
Posted 22 October 2007 - 07:11 PM
#14
Posted 22 October 2007 - 07:28 PM
I knew when I put that in that if it was wrong, our resident Apple Guru would call me on it, but damn now Smax has found support. :^0
#15
Posted 22 October 2007 - 07:40 PM
As Forest Gump said "Stupid is as Stupid does."
Almost as stupid as the notice I received today about the Seagate lawsuit. Which hinges on whether a Kilobyte is 1,000 bytes, or 1,024 bytes. Depends on whether you are using base 10 or 16. That difference has been known since before DOS and the IBM PC. But apparently when you advance that concept to a Gigabyte, you wind up 7 Megabytes short if its 1024 vs 1000.
#16
Posted 22 October 2007 - 10:09 PM
A Kilobyte (kB) is, by definition, 10^3 (aka 1000) bytes.
A Kibibyte (KiB) is, by definition, 2^10 (aka 1024) bytes.
See also: IEEE 1541
Surprisingly enough, it is the marketing departments that have this one correct. Programmers are are all too often using the term kilobyte incorrectly.
#17
Posted 26 October 2007 - 07:55 AM
just about every freedom you have
some one fought for!
and the only way to keep them is to fight 4 them!
If IPOD wants to keep the phone asis then I should not have to pay 4 the f n thing!
#18
Posted 26 October 2007 - 10:32 PM
#19
Posted 29 October 2007 - 12:04 AM
As of this date, legally as per federal law you are allowed to have your cellphone unlocked (this rule will be reviced soon).
Now, don't tell me that I loving a technology created under the laws of this country, because of a "higher interest" I will be limited to used it even if I correctly paid for it.
Stick arround for more.
#20
Posted 02 November 2007 - 01:56 PM
Sign In
Register
Help


MultiQuote
