FragmentedChicken@lemdro.idcake to Android@lemdro.idEnglish · 7 months agoApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comexternal-linkmessage-square109fedilinkarrow-up1265arrow-down111cross-posted to: technology@lemmy.worldtechnology@lemmy.mlbeeper@lemmy.ml
arrow-up1254arrow-down1external-linkApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comFragmentedChicken@lemdro.idcake to Android@lemdro.idEnglish · 7 months agomessage-square109fedilinkcross-posted to: technology@lemmy.worldtechnology@lemmy.mlbeeper@lemmy.ml
minus-squarewoelkchen@lemmy.worldlinkfedilinkEnglisharrow-up3·7 months ago To be fair that might just be a poor implementation? Maybe. Given that ProCall is a commercial product, it surely just reuses whatever MIT/BSD/Apache-licensed code exists instead of developing their own because that costs money.
Maybe. Given that ProCall is a commercial product, it surely just reuses whatever MIT/BSD/Apache-licensed code exists instead of developing their own because that costs money.