FragmentedChicken@lemdro.id to Android@lemdro.idEnglish · 1 year agoApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comexternal-linkmessage-square110fedilinkarrow-up1259arrow-down111cross-posted to: technology@lemmy.worldtechnology@lemmy.mlbeeper@lemmy.ml
arrow-up1248arrow-down1external-linkApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comFragmentedChicken@lemdro.id to Android@lemdro.idEnglish · 1 year agomessage-square110fedilinkcross-posted to: technology@lemmy.worldtechnology@lemmy.mlbeeper@lemmy.ml
minus-squaremisklinkfedilinkEnglisharrow-up2arrow-down1·edit-21 year agoApple broke Beeper Cloud too. If I had to guess, if Apple changed something that broke two different methods at the same time then it might be easier to fix by deducing from what they have in common.
minus-squarewoelkchen@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoIf I’m not confusing Beeper Cloud with something else and it’s indeed routed through real Mac, it block Apple uses may just be blocking the IP range.
Apple broke Beeper Cloud too. If I had to guess, if Apple changed something that broke two different methods at the same time then it might be easier to fix by deducing from what they have in common.
If I’m not confusing Beeper Cloud with something else and it’s indeed routed through real Mac, it block Apple uses may just be blocking the IP range.