News for hackers. Stuff that matters.
Re:Washington’s new anti-robocall law won’t stop the calls by awinter-py on Thursday December 26, 2019 @01:56PM (#21885841)
having a phone number will go the way of the landline

same with email addresses -- this is some combination of your identity and a license to spam you

spam protection is the main feature of gmail because email wasn't designed with fraud in mind -- an email system rebuilt from the ground up for 2019 would be safe for medical information, receipts, not be the giant password reset security hole that email currently is, and not allow randos to spam you

every new product designed in this century needs prevent fraud by design (including spam)

Re:Washington’s new anti-robocall law won’t stop the calls by JohnFen on Thursday December 26, 2019 @07:42PM (#21888141)
So then how would people reach me? Ignoring snail-mail, all means of reaching me involve either my phone number or email address.
Re:Washington’s new anti-robocall law won’t stop the calls by lmm on Thursday December 26, 2019 @11:30PM (#21889187)
Perhaps you'd give them single-use invites, or invites that included some form of certification path? I've noticed that Discord makes me go out of my way to hand out a reusable/non-expiring invite URL instead of a 1-day use-up-to-10-times link; obviously Discord's implementation relies on their hosting all the servers, but one could imagine a cryptographic equivalent that worked in a federated protocol.
Re:Washington’s new anti-robocall law won’t stop the calls by JohnFen on Monday December 30, 2019 @11:19AM (#21914364)
I don't use (or want to use) chat apps like Discord and such, though. It would also be a real challenge convincing the people I interact with routinely to start using such apps.
Re:Washington’s new anti-robocall law won’t stop the calls by lmm on Monday January 06, 2020 @12:14AM (#21966644)
Sure; my point is that we can imagine email/phone-like systems that would work the same way.
Re:Washington’s new anti-robocall law won’t stop the calls by bvanderplaats on Thursday December 26, 2019 @02:27PM (#21886029)
My company recently switched to MSFT Teams, and the other day I was thinking how difficult it would be to get spam through teams.

By design, only people part of our organization can communicate with each other. There (AFAIK) is no endpoint for my organizational teams account visible to other teams users outside my organization. For spam to occur, someone's account would need to be compromised (which would be found quickly) or a fake account somehow created by the org admin (which seems unlikely).

With email, the IT department is commonly spoofed, or the president, HR, etc. Most people can spot the differences, but with teams they would virtually never get any fraudulent messages.

Re:Washington’s new anti-robocall law won’t stop the calls by awinter-py on Thursday December 26, 2019 @02:50PM (#21886206)
Yes, though internal spam is a thing too. Chat tools are the prime driver of it
Re:Washington’s new anti-robocall law won’t stop the calls by hellisothers on Thursday December 26, 2019 @07:27PM (#21888064)
I suppose “social networks” are the replacement, you’re exchanging getting spammed by random actors you don’t know to a single actor (the social network).
Re:Washington’s new anti-robocall law won’t stop the calls by foobarian on Thursday December 26, 2019 @09:11PM (#21888568)
Aaaaand here we go reinventing the wheel of "trust graph." Key signing party anyone?