FragmentedChicken@lemdro.id to Android@lemdro.idEnglish · 2 years agoApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comexternal-linkmessage-square108linkfedilinkarrow-up1266arrow-down110
arrow-up1256arrow-down1external-linkApple responds to the Beeper iMessage saga: ‘We took steps to protect our users’www.theverge.comFragmentedChicken@lemdro.id to Android@lemdro.idEnglish · 2 years agomessage-square108linkfedilink
minus-squarewoelkchen@lemmy.worldlinkfedilinkEnglisharrow-up3·2 years 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.