"or other true facts about Apple)"

Except everything you just listed is mostly _not_ true or unique to Apple.

The apps that you launch? That was the developer certificate, not the app, over the same protocol for verifying certificates that is used in Windows SmartScreen and other systems.

The malware issue? Every statistic shows iOS has less malware than Android, so why exactly is that a complaint?

CPU down clocking? iOS warns you your battery is old, warns you this may cause slowness, a battery repair is like $50 or so, and it does that so that the thing doesn't crash and restart randomly just as Android phones will also do if their batteries are old.

Sure dude, it was not the app name sent in plain text but the app certificate, what is the difference ? Either Apple does not care about your privacy or they really care but are incompetent, chose one or other or both OR impress me with some mental gymnastics that makes Apple look good.

>(malware...)so why exactly is that a complaint?

Because some good people at Apple prepared emails to sent tot he victims but Tim decided that is bad for PR so fuck the victims. Aka people need to know that if Apple has to chose between PR or the customer PR is on top.

>CPU down clocking? iOS warns you your battery is old, warns you this may cause slowness,

You are the problem, Apple only does this after a class action lawsuit, you either are very misinformed or you are intentionally misinforming people. It is not an isolated incident where Apple is doing something fair for the user only when forced(similar cases with bad GPUs, keyboards,batteries)

"Sure dude, it was not the app name sent in plain text but the app certificate, what is the difference?"

Every OS on the planet will verify developer certificates to ensure that the app you are using is genuine. Windows uses SmartScreen, for example. Like I said, it's the same protocol (OCSP - Online Certificate Status Protocol) Windows and other apps use for certificate verification, so Apple is hardly doing anything wrong or being incompetent by not reinventing the wheel.

"Because some good people at Apple prepared emails to sent tot he victims but Tim decided that is bad for PR so fuck the victims. Aka people need to know that if Apple has to chose between PR or the customer PR is on top."

Understandable for three reasons: 1. It would cause major unwarranted panic that could cause additional attacks. I.e. A phishing scam saying "click here to be protected from the iPhone attack!" 2. The malware in question did not have any known function and didn't actually do anything or send anything to anyone. In other words, despite being prevalent, it was completely harmless. 3. The malware would be automatically removed from the device after a restart or software update, which most customers were likely enough to do naturally.

"You are the problem, Apple only does this after a class action lawsuit,"

Android quickly copied Apple and added warnings because Android never notified the user up to that lawsuit either. To the end user, even though Android didn't typically slow the device down, the Android phone would just crash and restart randomly when under too much CPU load.

>Every OS on the planet will verify developer certificates ...

In plain text? I know how this shit works, I digitally signed things before, and for this verification there is no need for internet. So copy pasted a lot of tech stuff there but it is complexly wrong. I could explain it how it works and why intenet is not needed but you could use google and figure it out, then find out what exactly Apple was checking(it was not the developer signiture).

>Understandable for three reasons: 1. It would cause major unwarranted panic that could cause additional attacks. I.e. A phishing scam saying "click here to be protected from the iPhone attack!"

Tim could hire some competent guy to write a clear email to prevent this. Also your point insinuates that you can cause a lot of damage to an iOS device with just an email and a link!! be careful Apple might not like you insinuating iOs is such terrible at security.

>2. The malware in question did not have any known function and didn't actually do anything or send anything to anyone. In other words, despite being prevalent, it was completely harmless.

Cure, malware sending data over the intenet behind the users back is harmless.

The conclusion is that Apple care more about PR, if Facebook would have sent one single bit of the users data Apple is putting a big article in the newspaper, if some malware is sending the exact same bit of data Apple changes it's mind last minute and keeps it hidden from the user.

>Android quickly copied Apple a

Ah, OK so Apple and Google shit stinks as bad, nothing new... Apple and Google are in the same boat, just one has some better PR and a big army of fanboys. Luckily the users found out and a judge forced this assholes companies to confess, otherwise next time the storage would say 500Gb but in reality would be half.

"In plain text? I know how this shit works, I digitally signed things before, and for this verification there is no need for internet. So copy pasted a lot of tech stuff there but it is complexly wrong. I could explain it how it works and why intenet is not needed but you could use google and figure it out, then find out what exactly Apple was checking(it was not the developer signiture)."

Actually, you do need the internet to ensure that the certificate was not revoked. This is partly why Apple put in the whole App Notarization thing in Catalina, because when you Notarize the app, MacOS can check if the Notarization was revoked whereas a simple Developer Certificate from a security company is a harder thing to revoke on demand or to check the authenticity of.

Notarization gives Apple, for better or worse, to immediately revoke a Developer Certificate without the need to check in with the Developer and have the developer signing certificate revoked from GeoTrust or whoever issued it. The Mac then checks in with Apple servers if the notarization is valid, and if it is valid, the app runs; and if it isn't valid, it knows it's been tampered with and revokes the app.

One benefit of Notarization is that it helps protect Apple and MacOS users from developer supply-side attacks like XcodeGhost. If the developer was compromised resulting in the code's legitimate source being poisoned and a hacked update was distributed, Apple could still immediately revoke that app because the Mac checks in when online.

"Tim could hire some competent guy to write a clear email to prevent this. Also your point insinuates that you can cause a lot of damage to an iOS device with just an email and a link!! be careful Apple might not like you insinuating iOs is such terrible at security."

I said Phishing Scam. A scam where you enter your credit card info for a fictional security software. Not all scams require a software hack.

"Cure, malware sending data over the intenet behind the users back is harmless."

Researchers analyzed it and concluded that it sent nothing back to the hackers. So it was indeed harmless. Apple also knew that their updates have a 90%+ opt-in rate, so when the next update went out, most users would have it automatically removed, and anyone who didn't update would likely restart their iPhone at some point, in which case AppleMobileFileIntegrity would detect and kill it.

"Ah, OK so Apple and Google shit stinks as bad, nothing new... Apple and Google are in the same boat, just one has some better PR and a big army of fanboys. Luckily the users found out and a judge forced this assholes companies to confess, otherwise next time the storage would say 500Gb but in reality would be half."

What BS are you spouting?