5 ms·

"It will be aimed at educating students, parents and teachers about the dangers of technology, including the depression that can come from heavy use of social m

"It will be aimed at educating students, parents and teachers about the dangers of technology, including the depression that can come from heavy use of social media." So, treating the symptoms rather than the disease, and at any rate nothing to do with these companies' pervasive and invasive data practices. Maybe they still have positions in their former employers, I don't know, but following the money will have to be a task for the future. All I can say is, "good luck." I'm sure some good speaker fees and book deals will come of this.

dang 9y ago
Please don't post reflexively dismissive comments to HN, especially when talking about other people's work, and extra-especially when it's the first comment to a thread. You might have a good point, but the genre itself drowns it out in a medium-is-the-message way. Discussions are sensitive to initial conditions and we're hoping that HN can be better than that. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- whatshisface 9y ago
  I think the pattern where the comments usually disagree with the article is healthy. It's a point-counterpoint argument structure, where the odd layers in the tree are arguing opposite to the even layers. The article makes its case, the first comments make the case that was missing from the article, the replies make the case missing from them... and so on.
  - dang 9y ago
    You're right, and we're not asking commenters to always agree with an article—but when disagreeing, to reflectively engage rather than reflexively dismiss. The article doesn't necessarily deserve such treatment, but the community does. We all share an interest in HN being a place for quality discussion, and this is how quality discussion emerges. It is most important early in the thread, because discussions are sensitive to initial conditions and the blank page is most vulnerable to rapid, shallow responses. By the time the more thoughtful ones have had time to emerge, the thread is often already choked by faster-growing weeds.
- rhizome 9y ago
  I read the article before posting, it's not reflexive.
  - dang 9y ago
    I believe you, but the comment itself contains one commonplace criticism ("data practices"—an important issue, but not so relevant in this context and very widely discussed elsewhere) followed by two cheap insinuations. That's not good enough. That combo of shallow and inflammatory is exactly what takes threads into hot mediocrity. That's a bit harsh and I definitely don't mean to pick on you. It's a systemic problem. I'm hoping we can gradually persuade the community to be more conscious of it.
Fnoord 9y ago
> So, treating the symptoms rather than the disease If you want to convince people with the point you're trying to make you I suggest you address the why and come up with one or more alternative, viable solutions. IOW, in short you must be constructive and I gave two examples how. What I quoted from you reminds me of Schneier's essay Data Is a Toxic Asset [1]. I'm not as intelligent as Bruce Schneier so instead of using my own interpretation I will quote his essay instead. The relevant part in understanding the why: > There are three reasons. The first is that we're in the middle of the hype cycle of big data. Companies and governments are still punch-drunk on data, and have believed the wildest of promises on how valuable that data is. The research showing that more data isn't necessarily better, and that there are serious diminishing returns when adding additional data to processes like personalized advertising, is just starting to come out. > The second is that many organizations are still downplaying the risks. Some simply don't realize just how damaging a data breach would be. Some believe they can completely protect themselves against a data breach, or at least that their legal and public relations teams can minimize the damage if they fail. And while there's certainly a lot that companies can do technically to better secure the data they hold about all of us, there's no better security than deleting the data. > The last reason is that some organizations understand both the first two reasons and are saving the data anyway. The culture of venture-capital-funded start-up companies is one of extreme risk taking. These are companies that are always running out of money, that always know their impending death date. And some solutions: > We can be smarter than this. We need to regulate what corporations can do with our data at every stage: collection, storage, use, resale and disposal. We can make corporate executives personally liable so they know there's a downside to taking chances. We can make the business models that involve massively surveilling people the less compelling ones, simply by making certain business practices illegal. Some of his other essays as well as his most recent book Data and Goliath also covers the subject (and also addresses solutions though the solutions are unfortunately not easy; they're difficult). In one of the chapters he suggests taking a smartphone with you is a conscious choice and that we should shift from a default always taking it with you to seeing the pros and cons of such a decision. [1] https://www.schneier.com/blog/archives/2016/03/data_is_a_toxic.html https://www.schneier.com/blog/archives/2016/03/data_is_a_tox...
- rhizome 9y ago

dang 9y ago

Please don't post reflexively dismissive comments to HN, especially when talking about other people's work, and extra-especially when it's the first comment to a thread. You might have a good point, but the genre itself drowns it out in a medium-is-the-message way. Discussions are sensitive to initial conditions and we're hoping that HN can be better than that. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

whatshisface 9y ago
I think the pattern where the comments usually disagree with the article is healthy. It's a point-counterpoint argument structure, where the odd layers in the tree are arguing opposite to the even layers. The article makes its case, the first comments make the case that was missing from the article, the replies make the case missing from them... and so on.
- dang 9y ago
  You're right, and we're not asking commenters to always agree with an article—but when disagreeing, to reflectively engage rather than reflexively dismiss. The article doesn't necessarily deserve such treatment, but the community does. We all share an interest in HN being a place for quality discussion, and this is how quality discussion emerges. It is most important early in the thread, because discussions are sensitive to initial conditions and the blank page is most vulnerable to rapid, shallow responses. By the time the more thoughtful ones have had time to emerge, the thread is often already choked by faster-growing weeds.
rhizome 9y ago
I read the article before posting, it's not reflexive.
- dang 9y ago
  I believe you, but the comment itself contains one commonplace criticism ("data practices"—an important issue, but not so relevant in this context and very widely discussed elsewhere) followed by two cheap insinuations. That's not good enough. That combo of shallow and inflammatory is exactly what takes threads into hot mediocrity. That's a bit harsh and I definitely don't mean to pick on you. It's a systemic problem. I'm hoping we can gradually persuade the community to be more conscious of it.

Fnoord 9y ago

> So, treating the symptoms rather than the disease If you want to convince people with the point you're trying to make you I suggest you address the why and come up with one or more alternative, viable solutions. IOW, in short you must be constructive and I gave two examples how. What I quoted from you reminds me of Schneier's essay Data Is a Toxic Asset [1]. I'm not as intelligent as Bruce Schneier so instead of using my own interpretation I will quote his essay instead. The relevant part in understanding the why: > There are three reasons. The first is that we're in the middle of the hype cycle of big data. Companies and governments are still punch-drunk on data, and have believed the wildest of promises on how valuable that data is. The research showing that more data isn't necessarily better, and that there are serious diminishing returns when adding additional data to processes like personalized advertising, is just starting to come out. > The second is that many organizations are still downplaying the risks. Some simply don't realize just how damaging a data breach would be. Some believe they can completely protect themselves against a data breach, or at least that their legal and public relations teams can minimize the damage if they fail. And while there's certainly a lot that companies can do technically to better secure the data they hold about all of us, there's no better security than deleting the data. > The last reason is that some organizations understand both the first two reasons and are saving the data anyway. The culture of venture-capital-funded start-up companies is one of extreme risk taking. These are companies that are always running out of money, that always know their impending death date. And some solutions: > We can be smarter than this. We need to regulate what corporations can do with our data at every stage: collection, storage, use, resale and disposal. We can make corporate executives personally liable so they know there's a downside to taking chances. We can make the business models that involve massively surveilling people the less compelling ones, simply by making certain business practices illegal. Some of his other essays as well as his most recent book Data and Goliath also covers the subject (and also addresses solutions though the solutions are unfortunately not easy; they're difficult). In one of the chapters he suggests taking a smartphone with you is a conscious choice and that we should shift from a default always taking it with you to seeing the pros and cons of such a decision. [1] https://www.schneier.com/blog/archives/2016/03/data_is_a_toxic.html https://www.schneier.com/blog/archives/2016/03/data_is_a_tox...

rhizome 9y ago