Re:Apple needs to change iPhone’s call UI because robocalls ...
by sofaofthedamned on Wednesday December 26, 2018 @04:30PM
(#18765088)
I used to work in the mobile space for 7 years and i'm still amazed nobody has proposed and monetized a solution to SS7 being unfit for purpose. The reason it's not happened is nobody wants to spend money on even talking about the fix, never mind implementing it.
The sheer number of scammers and nation state actors that have taken advantage of this is mind-blowing, but we still use SMS as a 2FA.
If we have telephony providers responsible for these breaches the problem will disappear in 6 months.
Re:Apple needs to change iPhone’s call UI because robocalls ...
by awakeasleep on Wednesday December 26, 2018 @04:43PM
(#18765197)
I worry you're missing my point!
It's not "spending money on the fix"... it's "killing our largest revenue stream"!
Re:Apple needs to change iPhone’s call UI because robocalls ...
by sofaofthedamned on Wednesday December 26, 2018 @04:58PM
(#18765286)
Wasn't missing your point, we're on the same page, hence my point about personal responsibility being the solution.
It's anologous to the web but that is on the way of being fixed - csrf, cors etc.
Re:Apple needs to change iPhone’s call UI because robocalls ...
by gnicholas on Thursday December 27, 2018 @01:58PM
(#18771591)
Thanks for posting! If I had to guess, the post dropped down because it tripped the flame war sensor, which I understand to be based on a ratio of comments/upvotes. When this happens inadvertently (not a true flame war), you can email the mods ([email protected]) and ask them to look into it. They're very responsive!
That said, the decisions in Apple's client side software are atrocious for the considerations of 2019.
Aside: No idea why my post went from #1 on HN to the third page in under 30 minutes, I thought we were having a fruitful discussion here