in the 90s there were no APIs you would just debug resident memory and network buffers to reverse engineer the API & IPC Am I old or do people have higher expectations now?
The author of this article was also the CEO of Beeper. They did just that and released an iMessage client for Android in December 2023. Apple proceeded to ban users of that client, launched a smear campaign against the company and implemented countermeasures until Beeper gave up on the whole endeavour. Apple has lots of options at their disposal to frustrate any attempts to reverse engineer their APIs, and have shown…
Apple restricts Pebble from being awesome with iPhones
661–670 of 1001 posts
Re: Apple restricts Pebble from being awesome with iPhones
#662Earlier quoted context omitted.
I probably dont get your sarcasm. But I never had a problem with Lightning. In the long run, I like the switch to USB-C... But when I got my first iPhone, USB-C wasn't invented yet, so... Also, I like the AppStore for its reviews, and would actually NEVER activate an alternative appstore. No need to weaken my security on purpose. I know, its apparently an unpopular opinion here, but that is mostly because many people…
Yup, Apple made Lightning because USB-C wasn't a thing yet and MicroUSB is awful. Lightning is a whole lot better than MicroUSB, and they've been using it since 2012 . MiniUSB B was pretty OK, Micro was just way too thin to be stable and would snap off frequently, in addition to being not very secure and hard to orient. Mini was thicker though, so while it worked fine for the HTC Apache and other Windows Mobile phone…
if the worst thing is someone else's code then someone else's hardware
Re: Apple restricts Pebble from being awesome with iPhones
#663Earlier quoted context omitted.
You obviously know that's not possible. They are private APIs kept for Apple's ecosystem lock-in.
Private API is an oxymoron. If it’s a private implementation, then there’s a lot of work that would need to be done to make it API!
Re: Apple restricts Pebble from being awesome with iPhones
#664Earlier quoted context omitted.
Don't forget the classic "Oh, that 3rd party app/feature is so popular, I bet we could build a identical/slightly less useful thing ourselves so people don't have to use other things than Apple software ever"
I've never understood this Apple criticism (scherlocking). Someone built a search for your files, so it's not right for Apple to build a pretty key feature into the OS? There's a lot of fair criticisms of Apple, but they don't have to be absolutely first at everything or never enter the market.
Re: Apple restricts Pebble from being awesome with iPhones
#665Earlier quoted context omitted.
If you want to do and fight, use Linux. Apple made their intentions clear decades ago.
Better than voting with your wallet is voting with your vote and getting regulations in place.
Re: Apple restricts Pebble from being awesome with iPhones
#666Re: Apple restricts Pebble from being awesome with iPhones
#667Earlier quoted context omitted.
You're being sarcastic, but isn't this all just... correct? Yes, I do trust the company that developed Secure Enclave more than I trust random BLE firmware in a $49 Alibaba watch. More importantly -- my great-uncle can trust the same thing, because Apple has spent decades building that trust. Consumers generally should not trust random hardware. Apple is not random hardware.
Google, Samsung, Pebble, Amazon, Microsoft, Sony, etc. have also spent decades building trust and don't build random hardware. But that doesn't matter because Apple locks them all out and insists you remain within their walled garden where it alone profits from you. If you don't want a future where you have to buy Apple milk to put in your Apple fridge (because the fridge stops refrigerating if you try putting any ot…
- requires immense development effort and expansion of security surface area
- STILL offloads trust to Samsung, Google, etc
The hyperbole here is a little hysterical. Apple doesn’t totally lock out third parties. In the smartwatch example, it is a very specific set of features which involved passing data (which users expect to be e2e encrypted!) back to Apple. That’s an extremely hostile security environment! Product tradeoffs would absolutely have to be made in order to support arbitrary third parties! I don’t think it’s fair to just demand that Apple make their product worse without at least exploring the balance.
Re: Apple restricts Pebble from being awesome with iPhones
#668Earlier quoted context omitted.
Couldn't you make that argument for literally any anticompetitive practice? Like in the 1990s: "Microsoft isn't making an OS for people that want to try different browsers"
Yes, you could. It's indeed troubling to see this mindset on HN. We have an overflow of professional "explainers" these days, we need more doers and fighters.
I ran debian as my daily driver for like half my life; now I’m on mac and never have to worry about my friggin wifi driver.
Re: Apple restricts Pebble from being awesome with iPhones
#669Re: Apple restricts Pebble from being awesome with iPhones
#670Earlier quoted context omitted.
Should be, but BT stacks are super crap and it's hard to truly guarantee that. Pretty sure they do not currently require the highest (actually proper) security level from everyone.
Given that Apple controls the entire hardware and software stack, can't they guarantee messages are encrypted and refuse to send them if they aren't? It seems like they're refusing unconditionally and claiming security instead of actually requiring security.
It's a whole another system outside of Apple's control and some mutually agreed upon Bluetooth LE elliptic key does nothing to protect it in its entirety. It still leaves cryptographic mistakes, side-channels and all other vulnerabilities.
Like, what does https:// or transport encryption in general really say about the website's security to you? Not much besides transport, does it?
Now we want to expose more than notification contents over Bluetooth (LE)? Are we sure? It has to be carefully designed.