71–80 of 280 posts
Earlier quoted context omitted.
If a plane crashed, and the company that manufactured the plane was fined because they had an engineering bug, no one would blink an eye.
Yes, there is a qualitative difference between a plane crashing and people dying and 69 million photos being leaked. If you have trouble understanding the difference you should probably see a therapist.
Earlier quoted context omitted.
> I don't know if this is a GDPR violation or not (as someone else asked), but if it is, I hope we start actually seeing action of these sorts of things. Sounds like you're suggesting that we criminalize software bugs.
Yes, I am suggesting that. I don't necessarily think jail time is the right thing, but I do think something like meaningful fines are more than reasonable for major software bugs that cause these kinds of breaches of privacy. It will make larger companies like this be much more careful when money is on the table for them to lose. To me, if we can criminalize something like a major oil spill such as BP/Deepwater Horiz…
The problem is that we're all giving our data away to these "free" platforms. That makes it difficult for a user to argue that they've "lost" something of value when there's a breach. But of course the user has lost something of value. Facebook has built their entire company around the value of our information but we let them have it both ways. It's valuable when they're selling it but worthless when they fail to protect it. Statutory damages for data breaches would deter negligence and (partially) compensate users who have been victims of data breaches.
Earlier quoted context omitted.
Yes, there is a qualitative difference between a plane crashing and people dying and 69 million photos being leaked. If you have trouble understanding the difference you should probably see a therapist.
It's just too bad that all crimes are punished by death. Awfully unfair and disproportionate in most cases.
>It's just too bad that all crimes are punished by death. Awfully unfair and disproportionate in most cases.
What are you even responding to? Explain this to me I'm too stupid to understand how your comment makes any sense in any context.
It's too much to hope that Facebook takes a hint from Google and shuts down its social network to preserve user privacy, right?
On this topic, does anyone know if photo access granted to facebook apps on ios means facebook will upload all photos in the background? Have never seen an analysis of it.
It's too much to hope that Facebook takes a hint from Google and shuts down its social network to preserve user privacy, right?
Google didn't shut down Google+ to preserve user privacy. Not sure if that's what you're implying with your comment-- I hope it's not.
They accelerated the planned shutdown for exactly that reason.
Earlier quoted context omitted.
If a plane crashed, and the company that manufactured the plane was fined because they had an engineering bug, no one would blink an eye.
This is more akin to the manufactoring company finding a defect that may or may not have contributed to a crash. Facebook hasn't said anything about if this bug was actually exploited
> "We're sorry this happened." That about sums it up for all these privacy breaches these days. It's getting to the same level of "thoughts and prayers" for tragedies. No actual change or consequences for the problems happening, just empty "sorries" and "promises" that it won't happen again/they'll get it fixed. I don't know if this is a GDPR violation or not (as someone else asked), but if it is, I hope we start act…
Genuinely curious on your view: what is an appropriate response?
CRIPPLING fines to start. Or shut down the freaking company if you can't secure it. Not everything is forgiven with a "we're sorry for 27845th time." Private pictures can and do ruin lives. (We can question the wisdom of posting private pics on FB but after all it's a huge company and they said they're private)
> "We're sorry this happened." That about sums it up for all these privacy breaches these days. It's getting to the same level of "thoughts and prayers" for tragedies. No actual change or consequences for the problems happening, just empty "sorries" and "promises" that it won't happen again/they'll get it fixed. I don't know if this is a GDPR violation or not (as someone else asked), but if it is, I hope we start act…
> I don't know if this is a GDPR violation or not (as someone else asked), but if it is, I hope we start actually seeing action of these sorts of things. Sounds like you're suggesting that we criminalize software bugs.
Earlier quoted context omitted.
> I don't know if this is a GDPR violation or not (as someone else asked), but if it is, I hope we start actually seeing action of these sorts of things. Sounds like you're suggesting that we criminalize software bugs.
Hammurabi's code (~1700 BC) includes this about building: Building Code 229. If a builder builds a house for a man and does not make its construction sound, and the house which he has built collapses and causes the death of the owner of the house, the builder shall be put to death. 233. If a builder builds a house for a man and does not make its construction sound, and a wall cracks, that builder shall strengthen tha…