Re:Apple restricts Pebble from being awesome with iPhones
by Nextgrid on Tuesday March 18, 2025 @02:00PM
(#43402573)
It doesn't need to be a plugin ecosystem - no third party code needs to run within the iMessage processes/sandboxes/containers. In fact, no third-party code needs to run at all on the phone - all that's needed is to expose an API over BLE that allows previously authorized external devices to query/send messages.
[ Parent
| on HN ]
Re:Apple restricts Pebble from being awesome with iPhones
by usrusr on Tuesday March 18, 2025 @03:02PM
(#43403484)
In defense of the "it's security!" position (which is not mine): I think they mean a similar vulnerability could exist on the client side of the API. As in someone sends manipulated media that targets a vulnerability on the third party device, the media gets forwarded through the API, now that compromised third party device does bad things over the API.
Personally, I think that it's really just a convenient third party lockout excuse, but the argument isn't quite as bad as it may seem at first glance.