News for hackers. Stuff that matters.

A comment on FCC will require phone carriers to authenticate calls by June 2021 [pdf]. Parent comment

Re:FCC will require phone carriers to authenticate calls by ... by grahamburger on Tuesday March 31, 2020 @05:18PM (#22742705)
Recent versions of Android have an option to automatically screen callers who are not in your contact list. The caller gets a robot asking them why they're calling, and you can view the transcript of their response in real time and decide whether or not to answer.
[ Parent | on HN ]
Re:FCC will require phone carriers to authenticate calls by ... by SketchySeaBeast on Tuesday March 31, 2020 @05:22PM (#22742750)
I thought that was Pixel only option - I'll have to dig in and see if it's available on a Samsung.
[ Parent | on HN ]
Re:FCC will require phone carriers to authenticate calls by ... by ChuckMcM on Tuesday March 31, 2020 @05:24PM (#22742769)
As I recall this was a Google Voice feature as well.

My mobile carrier puts "scam likely" on calls that its algorithms have determined are likely spam, I wish there was an android option to just not ring the phone if that was the caller ID name.

[ Parent | on HN ]
Re:FCC will require phone carriers to authenticate calls by ... by bonestamp2 on Tuesday March 31, 2020 @05:39PM (#22742915)
My carrier was doing that but I haven't seen it on any spam calls lately.
[ Parent | on HN ]
Re:FCC will require phone carriers to authenticate calls by ... by unclebucknasty on Wednesday April 01, 2020 @01:18AM (#22745928)
I've used this feature and each time it occurs to me that the next step for spammers will likely be to simply leave the message, as they will still get an impression via the transcript.
[ Parent | on HN ]
Re:FCC will require phone carriers to authenticate calls by ... by texasbigdata on Tuesday March 31, 2020 @07:12PM (#22743789)
It's nice but buggy!
[ Parent | on HN ]