Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Getting away with it? (Score 3, Informative) 350

It's not a question of ownership. It's a question of warranty. He still owns his (now-bricked) phone.

In this case, the dude dropped his phone, gets it repaired at some no-name shop with dodgy parts, then complains when the security loophole the dodgy parts used got closed. If anything, the fault lies with the shop that did the repair.

Hell, Apple told him they'd do out-of-warranty replacement for it (not sure what that costs, but likely still less than full price), and that's because the problems began when he dropped it (which is not covered under warranty anyway, though some 3rd-party sellers do offer such warranty protection for a nominal fee).

Fair warning: If I bought anything from any other OEM and went through the same rigamarole, I'm certain that I'd get the same (or worse) treatment from the OEM... so this isn't just an Apple thing.

(...and this boys and girls, is why I buy just-behind-bleeding-edge Android stuff, so a total loss of the phone is only like $200, not $600 or more).

Comment Re:Solution! (Score 2, Insightful) 350

Dude in the Balkans could have his phone repaired at an Apple shop when he got home, right?

Not trying to be a dick or anything, but honestly - using a gray-market security-related part *should* get that result. If my device is stolen, I'd want that to happen - if only to prevent some schmuck from plugging in something with hacked firmware to bypass the fingerprint sensor.

Comment Re: Hah! (Score 1) 634

The lottery has MUCH higher odds.

You do realize that the lottery, say Powerball, has 6 numbers, with each number having a far larger set of outcomes, right? The first five numbers can cough up anything from 1 - 69, and the sixth number anything from 1 - 26. *That* is why the odds are much higher with a lottery of that type.

By contrast, six coin tosses (each toss producing one of two outcomes) by contrast only has something like 64 possible combinations, max...

Comment Nah - not seeing that happen... (Score 3, Insightful) 220

That would get more than a bit expensive, wouldn't you think? I meant for the manufacturer, not the individual consumer (who also gets shafted).

I'll explain - the R&D into making everything fail at once (or enough to brick the device) would never be recouped...

* too much chance of the customer jumping ship to a competing brand that promises that their widget lasts x% longer.
* too much chance that the failure wouldn't fail gracefully, causing something lawsuit-worthy
* too much chance that the failure would fail gracefully, but do so at the wrong time, again causing lawsuits
* too much chance that you mis-time your intentional MTBF, causing your entire customer base to simply stop using that class of device (after all, I don't *need* a smartphone to eat/sleep/shit/whatever, and if the cost is too high to keep replacing them, I'll simply do without.)
* too much chance that some group like Greenpeace (or worse) would use that pre-planned failure to whip up animosity towards you and your company. ...sure there's lots more involved, but think about this: some breakages can be repaired at relatively little cost, such as a cracked screen. Because of this, replacing an entire fairly-new phone (and then blowing all that time configuring/syncing the replacement) because the screen cracked is asinine (doubly so when you consider things like device insurance).

Just at first blush, I don't see this idea working at all... it would require everybody in the industry to do it at the same time, and further require that a struggling company not 'cheat' by making and selling more durable products.

Comment Re:first (Score 1, Interesting) 697

first

rm -rf /first/*.*

By the by, the above 'code' snippet may well brick a *nix box - use at your own risk. I saw first-hand that doing an rm -rf *.* was perfectly capable of blowing away an entire install (including all mounted devices), no sweat - at least as late as 2006 when a junior admin I once worked with made that rather horrendous typo in his regex...

But overall, why the hell is this news? I mean, every OS has this problem (see also the ancient deltree, or the newer rd /s, or getting stupid with the GUI Disk Utility in Windows or OSX, etc.)

Boys and girls, this is why you don't give ordinary folks admin/root/wheel/whatever privileges, eh?

Comment Re:Article paid by Apple to boo over it. (Score 4, Informative) 455

You want log files? F-U, Apple fanboys don't need no stinkin log files so they don't exist despite Unix being one of the pioneers of this concept. You want an error code? Nope, can't help you there, they don't exist; you're lucky if you're told that a problem occurred at all.

Huh? What are you talking about?

Slashdot Top Deals

Save a little money each month and at the end of the year you'll be surprised at how little you have. -- Ernest Haskins

Working...