> These techniques posed significant risks to user security and privacy, including the potential for metadata exposure and enabling unwanted messages, spam, and phishing attacks.
Didn’t it recently come to light that apple have been “exposing” that metadata to government agencies for years? Maybe they should stop exposing metadata rather than blaming others for replicating their implementation!
How does a 3rd party implementing their API mean there will be “unwanted messages, spam and phishing attacks”? Are they accusing the 3rd party of doing that, or do they believe 3rd party software is inherently inferior to their own (which constantly needs security updates).
Because by abusing an older style auth method, they skip a lot of the checks required to start iMessaging people currently.
This methodology can be abused by SMS scammers, phishers, etc to easily target the iMessage network that users may often feel has a higher default level of trust.
> These techniques posed significant risks to user security and privacy, including the potential for metadata exposure and enabling unwanted messages, spam, and phishing attacks.
Didn’t it recently come to light that apple have been “exposing” that metadata to government agencies for years? Maybe they should stop exposing metadata rather than blaming others for replicating their implementation!
How does a 3rd party implementing their API mean there will be “unwanted messages, spam and phishing attacks”? Are they accusing the 3rd party of doing that, or do they believe 3rd party software is inherently inferior to their own (which constantly needs security updates).