sparky@lemmy.federate.cc

Lead administrator of federate.cc and its services. Please don’t DM me for support with federate.cc, make a post in /c/meta instead.

Originally from Fort Lauderdale 🇺🇸, lived many years in Vienna 🇦🇹, now living in Setúbal 🇵🇹. Software engineer specialized in Apple platforms. 🌎

  • 4 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle













  • Former Apple engineer here. This architecture isn’t ideal if you intend the service to be portable - but we didn’t! Knowing the messages can only originate from a sealed application on a first party device eliminates a whole class of spam and security problems.

    Beeper’s implementation spoofs Mac keys and requires you trust them with your Apple ID credentials if you want to be able to take full advantage of iMessage.

    It’s just pointless. A huge security risk for Apple users and to zero benefit for Android users. Let Apple implement RCS as they promised and move on. Isn’t everyone on Telegram or WhatsApp anyway…?






  • Former Google and current Apple engineer here; this is definitely an insecure workaround with a lot of flaws. I think Beeper is basically doing the same.

    The reality is that while we do have a lot of walled garden policies for business reasons (which I don’t love), iMessage and FaceTime are a bit more complicated than that, tightly coupled around the hardware encryption and keystore in the TPM in our devices. Unwinding this would be undesirable from a compatibility perspective as it would break any Apple devices not updated immediately to new OS versions that change the encryption scheme.

    So the only way to plug into iMessage per se is a weird workaround like this where you basically AppleScript automate the Messages app on a Mac with its shields down.

    There’s not a great way to fix this problem which is largely why we are bringing RCS support to iOS 18 to hopefully make such things moot.

    But that said even as an employee I don’t think iMessage is a great example of a modern chat app. I mean, it’s better than SMS which is what it sought out to replace. But compared to an actual chat app - something like Telegram - it doesn’t hold up.


  • This is a really disingenuous argument even for /c/android. iOS has many pitfalls with the walled garden effect but it also has many advantages with regard to software quality, consistency and performance (particularly at an API level, speaking as a developer for both platforms). If we write them off as bad, dumb or irrelevant then we forego the opportunity to improve our own apps and Android as a platform. Google does not have a monopoly on good ideas nor on technical users - one could note that Android itself is developed on Macs, as Silicon Valley developer workstations are almost universally Apple hardware…