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-square107fedilinkarrow-up1263arrow-down110cross-posted to: [email protected][email protected][email protected]
arrow-up1253arrow-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-square107fedilinkcross-posted to: [email protected][email protected][email protected]
minus-squarewoelkchen@lemmy.worldlinkfedilinkEnglisharrow-up3·1 year 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.