4 ms·

You mean the company who controls the protocol, and the clients, and the servers for a given service somehow found a way to stop a third-party from utilizing th

• sonicanatidae 3y ago
  Make sure you mention the tubes!
• rplnt 3y ago
  And IIRC it used some old OSX binaries to do so? Just terminating the access might be a lucky outcome if that's the case, considring the money involved.
  • tadfisher 3y ago
    pypush uses the old binary pulled from macOS. Beeper Mini uses another workaround for the device UUID/serial/etc. requirement.
    • turquoisevar 3y ago
      > Beeper Mini uses another workaround for the device UUID/serial/etc. requirement. Have you got a source on that? As far as I know, there's no workaround possible because the authentication blob is based on the UDID/serial. Put differently: without UDID/serial, there's no way of authenticating with the message servers. Beeper keeps referring to pypush when it comes to details in their write-up[0], and pypush, in turn, clearly states[1] the need for information like serial and UDID when dealing with the albert server and IDS registration request. As a “workaround,” they simply stuff fake serials, etc., and cross their fingers that it gets through Apple’s scoring mechanism. 0: https://blog.beeper.com/p/how-beeper-mini-works https://blog.beeper.com/p/how-beeper-mini-works 1: https://jjtech.dev/reverse-engineering/imessage-explained/ https://jjtech.dev/reverse-engineering/imessage-explained/
  • deleted 3y ago
    [deleted]