• Mongostein@lemmy.ca
    link
    fedilink
    arrow-up
    23
    ·
    11 months ago

    Makes sense because they were spoofing real machine IDs. People want to shit on apple for shutting it down, but I would be fucking pissed if I started getting other people’s messages and notifications while having mine go to someone else.

    Trying to build a business off of someone else’s services is scummy and Apple did the right thing. If they weren’t charging for it I might feel differently.

    • kick_out_the_jams@kbin.social
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      11 months ago

      If they weren’t charging for it I might feel differently.

      I don’t think they ever charged anybody, they suspended that idea after the first outage.

      Also, they were using their own fleet of Macs, hence why Apple was able to isolate them easily if they’re all centrally located.

      • Mongostein@lemmy.ca
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        11 months ago

        My understanding of it (and I could be wrong I’m not that invested in this) is that the first iteration used their Mac fleet, while the second iteration was spoofing IDs. This would be the third iteration.

        It was a few days ago I read this, I’d have to look up the source again

        I have no problem with this third iteration. There’s plenty of Mac users with android phones. If you’re using your own machine ID, have at ‘er.

    • EliasChao
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      but I would be fucking pissed if I started getting other people’s messages and notifications while having mine go to someone else.

      Was that ever the case though?

      I was under the impression that the spoofing the machine IDs part was only for “convincing” Apple servers that the request was from a valid Apple device, not that it would combine different people’s Apple ID’s messages in any capacity.