Many of us, as software developers, are taught to solve general problems instead of specific instances whenever we can. That's what I see as wrong with 99% of the commentary about this recently. Sure, there might be a bug in Facebook. Maybe it's a serious bug, and it really needs to be fixed. But it's a bug that manifests in many other places too. It's even possible that Facebook is neither the first nor the worst. Facebook doesn't have "assistants" that listen to your every word like Google and Amazon and Apple do. It doesn't have all of your email, or your entire search history, or the very OS on a device you have with you all the time. But I digress.<p>The real point is that targeting any "fix" too narrowly toward Facebook, or Google, or any one party doesn't fix it for the others. It might even distract from or interfere with development of a more general solution. But that's exactly the path a lot of people seem to be going. By all means, criticize Facebook if you think they've done something wrong, but <i>don't stop there</i>. Make sure you understand the full scope of the problem, and the options for addressing it <i>in a general way</i>, and the benefits or drawbacks of each approach. Progress doesn't come from everyone saying "me too" on a bug report. It comes from people talking about and then implementing ideas to make the bug stop happening <i>anywhere</i>. I've seen precious little of that.