You did a great job critiquing many people here on MacRumors too. The same thing happens every day here in the forums.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Wins Lawsuit Over Group FaceTime Eavesdropping Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
You did a great job critiquing many people here on MacRumors too. The same thing happens every day here in the forums.
Yes, let’s not forget this feature which lets anyone log into an admin account using the username "root" with no password when HighSierra was released.
I think he went to Pennypacker university
Apple would have just written it off!!!
The developers who speak up here, and call it coding error should rethink their profession.
This was not a coding error, it was a huge thing happened at tim privacy's company, there must be consequences.
Cant happen that someone spys at You because apple is to lazy or incompetent for testing a feature
This was not a coding error, it was a huge thing happened at tim privacy's company, there must be consequences.
Cant happen that someone spys at You because apple is to lazy or incompetent for testing a feature
So to extend that thought, anybody who has ever made a mistake on the job should rethink their profession? Don't think so, part of what makes a person (and organization) better is being able to incorporate past mistakes as a learning lessons. Most people, imo, who are great at what they do have the battle scars to prove they tried.
So in my own opinion, these people should not rethink their profession.
It's not the electrical current threshold at which the batteries no longer operate that Apple referenced in their statement but instead the threshold at which they start to trigger unexpected shutdowns at peak loads.
As a professional developer, and feeling pretty insulted by your attitude, I'd say that by the same rule, anyone whose English is as bad as yours should stop posting comments here. "it was a huge thing happened at tim privacy's company" doesn't even make any sense. I suppose the eternal rule applies here: Anything is easy if you're not the one who has to do it.
[doublepost=1557585678][/doublepost]
Android users expect rubbish. Their phone has shutdowns, they just shrug their shoulders and get on with their lives. iPhone users complain.
[doublepost=1557585934][/doublepost]
He wouldn't. He would have had to show actual damages. The claim that someone listened in to a call between him and a client is completely unsubstantiated. Not a shred of evidence. Even if someone had listened in, he would have had to show damages. But the lawyer doesn't suffer damages in this situation - the client _might_.
[doublepost=1557586033][/doublepost]
Your question doesn't make any sense to me.
All batteries age and die. Apple had a $29 sales in batteries, as a goodwill (IMO) gesture so customers could get extra life from their phones.
You're nitpicking.This is a win in every practical sense.
In a civil case, a judge is rarely going to dismiss a case with prejudice, because it is usually done after the judge makes a final determination of the facts of the case presented. Yes, the plaintiff theoretically could correct and refile, but as the judge points out, those defects are so glaring that they don't even meet the minimal bar to trigger consideration by the judge/jury.
[doublepost=1557590741][/doublepost]
What most people are upset about is that the American legal system, imperfect, but probably the overall finest in the world, has the unintentional, but serious problem of encouraging frivolous law suits. This happens because, unlike the English system where the "loser pays," there is little deterrence to unscrupulous lawyers filing lawsuits that innocent people have to incur enormous costs to defend. Thus, this encourages litigants to file simply to force people to choose from the incurring the time and expense, which may be ruinous, or settling.
The problem is exacerbated due to the enormous oversupply of attorneys as law schools have churned out lawyers without regard to supply and demand. Some, not all by any means, of these lawyers then survive by offering, even soliciting, clients by taking on cases "for free," with the hope of getting 33 to 40% of any settlement merely by filing an action, however meritorious.
The other problem often discussed here are "patent trolls," but that's another issue
Last edited:
Nothing like proving you don’t know anything about writing code. Why don’t you leave that discussion to those of us who actually do write code?
I already gave one example. Here’s a couple more (as simple as I can):
A developer has debugging/testing code in FaceTime. All it takes to activate this code is for a flag to be set to true. The developer should have removed this code for the final build, but left it in by mistake.
Normally this wouldn’t be a problem as the code wouldn’t be run since the flag wouldn’t be set. But a bug in another section of code mistakenly sets this flag, running code that shouldn’t be there, causing the FaceTime issue. The bug could be the user adding themselves back to a group call before the person answers (which is how this issue started).
This code doesn’t have to be for debugging. It could also have been for a new feature Apple is working on - the ability for parents to activate FaceTime on kids devices remotely to check up on them. Or for a device owner to activate FaceTime remotely on their stolen iPhone to try and get clues to recover it. Except a bug allowed this feature to activate for normal users.
Another issue is when developers are writing code and initially start their project. Often you will have a set of subroutines to perform various functions. At the beginning these routines are often placeholders that you fill in later. Often when creating such a routine you only code what you need to get it working, with the idea that you can go back and “clean up” your code later on and make it more robust (like adding in error checking). The problem is if a piece of code is working fine and never causing a problem you tend to forget about it. This can carry on to the point that a poorly written piece of code that never caused a problem ends up in the final build. Only then, when it’s stress tested by a large number of regular users (who always do things they’re not supposed to) do bugs appear.
People like to think developers never make mistakes or wouldn’t do anything like the “rookie” examples I gave. But it happens. Nothing nefarious at all - just simple (and common) mistakes a lot of developers make.
So unwanted software bug is on a same level as sexually assaulting actresses. Well done you.
And yes, this is sarcasm for you and those people who clicked LIKE on your comment.
And to finish in a good spirit, it is a lovely sunny day, so grilling is in order (probably me as a main course)
Last edited:
Well I wouldnt be using this lawyer
Suppose he will sue Apple for his reputation being tainted next...
We all fear that this is the kind of coding that lead to this incredible remote spying bug in Group Facetime in the first place. And everybody who does professional software development would be frightened if the uncoordinated approach you just tried to promote as "typical" was the actual standard.
No folks, that‘s not how software development is typically done, even if it might describe how that Facetime bug came to be. There exists well-proven patterns for software security and release management, and the fear that Apple just does not adhere to them, proven by that totally unnecessary Facetime remote bug, is the actual thing to discuss.
Trying to promote a small company’s quick hack coding strategies as the standard for a corporation like Apple that controls millions of devices through their software does not help to prevent these kind of problems.
You’re right of course. But if it were as easy as you suggest windows wouldn’t have 25 year old legacy vulnerabilities.
So folks, while **** happens with large scale development it ain’t easy to keep them bugs out. But I do agree there are processes and procedures.
Never said it‘s easy. It‘s annoying work and nobody (directly) loves you for that. Especially it‘s not about the "we‘re all so creative" part, but about the one that makes the creative work a valuable product. It‘s about discipline, patterns that have to be implemented and checked on a regular basis, and books and papers that have to be read.
I would not expect any three guy software company to be able to implement all that. But if you‘re doing systems engineering you usually are well paid for that work and can afford the effort. Apple definitively has the means to so, still we saw (and heard from insiders recently) that the current company culture does not exactly support sticking to that kind of annoying work at the moment.
Of course you will always have bugs. But like in other engineering areas you usually build in safeguards that don‘t let a single bug perforate the whole thing nor larger parts. And those safeguards cost you. Time, personnel, external skills and audits. Apple has to do so for their HW products, since the FCC demands these quality checks and certificates. They should adhere to similar quality measures for their software, without having to be forced by the government.
I think you would feel differently if you and your family lost everything due to its abuse. We were spied on in our home More than 21 times over a 3 week period by my now previous employer. Kinda makes you feel disgusting and violated in a sexual assault kind of way when they rub your face in how they watched and heard you have sex with your wife and you recall the times you were reading the news on your phone while in the bathroom or setting your phone down before bathing or checking your calls as you towel off. After they fire you because they hear and see your closed door/private life, family discussions with children, your married life arguments over money/bills, love spats/concerns and slander you all over town because they heard your plans for the future and if the next 10 years includes them as the previous 10yrs you had the job did, the bug seems a little nastier. It is alot nastier after they project you as a thief to everyone you used to have business/professional relationships with and give a heads up to the other local companies in your field after suddenly forcing you into a non compete before they “get you back”. A little nastier again when your home is foreclosed on and you get sued twice for the bills you now cant pay. I have had apple products since 07 and stuck with them solely for the security of them, yeah so nastier again when you realize your stupid too. Dont get me started on the fictional things people can invent when they hear and see pieces of things. Had this not happened i would still have my job and our family would have our home. My 6 yo wouldnt have paranoia issues that people are listening and all 4 of our children would still have their future. Who exactly does someone think they are to feel they are allowed to spy in someones home, on a device that doesnt belong to them over a connection they do not pay for or to belittle that loss because it didnt affect you. Imagine your camera and mic are on for the next 3 or more weeks and see if you feel the same. Its like a hit and run accident, they got out and said that dent was already there and that other spot will buff out and drove off.
[doublepost=1567702994][/doublepost]
If a mechanic says your brakes should work but they dont, are you no longer liable for the car you hit and the people in it that you hurt or killed? You are as well as the mechanic. If installed and bled correctly they will work but the car is test driven to ensure they are working properly and if not rechecked and re bled and corrected then test driven again to ensure safety and function. You could be lazy and just slap it together like a fast food hamburger then blame-shift when they fail because the you followed the instructions and they should have worked or you could test them forward, reverse, fast, slow, hard and soft twice to ensure your work and justify the trust someone placed in you to do the job.
Last edited:
Interesting story but a little hard to believe. If your employer spied on you that would be a criminal offense and he or she would be in jail. It's not comparable with a software bug that could be exploited to spy on someone.
As to the brakes it's not the same thing. It would be like if the mechanic didn't calculate the possibility of someone cutting your brake lines then they failed.
lol, but when it's other OEMs they don't get this kind of benefit of doubt.
What's the excuse for Siri listening and the judg have going on for several years?
Who says other OEMs don't get the same benefit of doubt - you? As far as Siri is concerned, by definition it has to "listen in" all the time - otherwise it wouldn't know when you're asking it "Hey Siri..." Secondly, who says there's an excuse for Siri sometimes letting humans review (not listen in) audio it captured? Apple says that this review happened to < 0.2% of audio recordings and that folks who enable Siri agree to it in the terms of service. But Apple agreed that this was not enough and agreed to give users an in-your-face option to opt out in the future. Case closed.
Ahhh yes, you see it would be a criminal offense you could prosecute had a company not deliberately done somethings that they did post this small harmless software glitch and people didn’t find it so “hard to believe”. I can promise you however, I have heard that many times getting to the point I am finally at with this and I would love to elaborate on the details but unfortunately at this time I cannot. BTW no one cut the brake lines they just caught the free fluid and didn’t mention the leak, the car manufacturer sold a lot of cars leaking as brand new then cleaned up the puddles and whistled as they walked away and later found the news broadcast about it hard to believe while I am sure many more people than just me are trying to find the pieces before they can even begin to pick them up. But better me than you right?
Again the glitch doesn't cause someone to exploit it so that's where your brakes analogy fails. The brakes would have to have a weak spot for a person to exploit. For example brake lines under the car that were easily accessible and cut. Since you made user name just to post this I'm guessing you're a victim of Apple's bug and your employer used it to spy on you? Again still illegal even if it's using a glitch or bug.