Federal authorities arrested a 58-year-old Colorado Springs man after unravelling the origin of a "Declaration Of War" that threatened harm or death to Elon Musk, owners of his Tesla vehicles, and members of President Donald Trump's Cabinet.
Messages from his burner phone, too, matched the number Payne had listed in his personal contact info while applying for unemployment benefits in February.
If you put your real name on it or associate that phone number with your name, then doesn’t that stop meeting the definition of a burner phone?
EDIT: I re-read the wording of the article, and I don’t think he used the burner phones number associated with his name as I posted before. The article says this:
"Messages from his burner phone, too, matched the number Payne had listed in his personal contact info while applying for unemployment benefits in February. "
It sounds like he used is REAL phone/number to apply for unemployment, but then at a later time he used is REAL phone to text a message to his burner phone. So the article is saying the “messages found on his burner phone” contained his REAL phone number. This would mean authorities would have had to have the burner phone in hand. So this wasn’t the way he was found, simply a way that it was confirmed it was him.
Sure he’s dumb but his failure gives an interesting insight into how wide the US dragnet on its citizens is. A mail address used to apply for unemployment has been indexed somewhere « just in case ». Nice.
Storage and indexing is cheap. From a usability perspective indexing makes sense: call centre staff can tell someone why their unemployment application has been denied/delayed etc.
From a security perspective, Google, Proton, and friends want to track failed login IPs so they can assign (internal) reputation scores to incoming requests.
It’s the sharing & cross enrichment that would bother me. That your unemployment office keeps a CRM with the info makes sense. That LEA has it all and more together with the gods know what else is what I would object to.
Same for how service providers store that info; there’s a fine line between storing enough and too much. Or too long. And not everything needs to be tied forever to the customer ; sometimes a hash or whatever does wonder for the legitimate purpose. Storing more is often « just in case I can market the data later » which I’m personally not agreeing with.
If you put your real name on it or associate that phone number with your name, then doesn’t that stop meeting the definition of a burner phone?
EDIT: I re-read the wording of the article, and I don’t think he used the burner phones number associated with his name as I posted before. The article says this:
"Messages from his burner phone, too, matched the number Payne had listed in his personal contact info while applying for unemployment benefits in February. "
It sounds like he used is REAL phone/number to apply for unemployment, but then at a later time he used is REAL phone to text a message to his burner phone. So the article is saying the “messages found on his burner phone” contained his REAL phone number. This would mean authorities would have had to have the burner phone in hand. So this wasn’t the way he was found, simply a way that it was confirmed it was him.
Yeah they try to paint the guy as some tech genius but frankly he was sloppy af
Yeah, not really a burner phone if you don’t burn it. Then it’s just a second phone.
Sure he’s dumb but his failure gives an interesting insight into how wide the US dragnet on its citizens is. A mail address used to apply for unemployment has been indexed somewhere « just in case ». Nice.
Storage and indexing is cheap. From a usability perspective indexing makes sense: call centre staff can tell someone why their unemployment application has been denied/delayed etc.
From a security perspective, Google, Proton, and friends want to track failed login IPs so they can assign (internal) reputation scores to incoming requests.
It’s the sharing & cross enrichment that would bother me. That your unemployment office keeps a CRM with the info makes sense. That LEA has it all and more together with the gods know what else is what I would object to. Same for how service providers store that info; there’s a fine line between storing enough and too much. Or too long. And not everything needs to be tied forever to the customer ; sometimes a hash or whatever does wonder for the legitimate purpose. Storing more is often « just in case I can market the data later » which I’m personally not agreeing with.
“No b-because he was a bad guy so we can accuse him of other bad guy stuff too!”
Inb4 police find “a mysterious white power” and never mention it again
I guess you mean white powder
White power is clearly very openly rampant in police institutions worldwide - although, I guess, the white powder isn’t far away either…
Not if it’s a Pixel 6 Pro!