The fact that they are taking uniquely identifiable information from you, and the fact that their company is as deep in the Ad game as Google, is more than damning enough.
662 karma · joined December 1, 2018
The fact that they are taking uniquely identifiable information from you, and the fact that their company is as deep in the Ad game as Google, is more than damning enough.
In general, when your diagnosis to a problem is "the people using my product are all just too lazy to use it right", the problem is almost always that your product is the problem.
Similarly, they can read whole books very quickly, but they do so by reading just the first sentence on every page. This is what gives them the superpower of reading large technical emails, and responding to them in seconds about a completely unrelated topic.
I very much suspect that who is elected has nearly zero effect on spying programs.
I think this is generally a symptom of current leadership practices, where the people making decisions about technical direction are not people who understand how their product functions. This generally isn't top leadership, but the upper and mid level management, who feel they need to "make their mark" on the product to get promoted.
Isn't this basically the idea behind snaps? Or is that more docker-like?
As someone who tried to do this... Ouch. Things like this are why X will still be around in 15 years.
My favorite part is when someone figures out "telemetry" includes the MAC address, and the dev team just goes completely silent.
I think you'll find that you've identified the target market for almost all modern film adaptations of science fiction novels.
There are two classes of damages police can enact on you in the US, both of which makes interacting with them in any capacity dangerous.
The first class is that they can completely ruin or end your life. This includes anything from killing you, leaving you with lifelong injuries or stress disorders, felony charges, etc. Anything that permanently scars your enjoyment of life.
The second class is non permanent, but extremely inconvenient damages. These are very common, take little effort or thought on their part, and ranges from impounding a car, charging you with a misdemeanor, harassing you, taking large sums of cash from your person, disturbing your house or belongings, trespassing you, holding important belongings or documents as evidence, etc.
Either of these classes of damages can be the result of an interaction with police, stemming from saying the "wrong thing", "acting nervous", "acting suspicious", being in the vicinity of a possible crime, being accused of witnessing an event, being too close while they are conducting police business, "making them feel uncomfortable or unsafe", being the victim of a crime, etc.
Each time you speak to police, you risk a chain of events occurring that result in one of these two classes of damages. It's just not worth it. They aren't worth talking to, given some of the possible outcomes.
For me, this is where the problem with got lies. I use so many of it's commands infrequently enough that I don't know where the weird disastrous edge cases are, where I should use.
I think git would greatly benefit from a topical man page; a list of common and uncommon situations that shows the recommended commands for solving them, and explains what those commands do. I know that hundreds of random "guides" exist, but are they outdated, are they cannon, do they have bugs? When your UI is esoteric, situational documentation is really important.
Don't forget all of the future losses by losing the trust of both the customers and the employees.
> it’s that prepping for them costs more than the loss from not being able to absorb them
This assumes that they can absorb these losses.
Not only do they remove flexibility, but they often introduce "magic" that is too difficult to debug when dealing with live industrial systems. It's fairly simple to go through a bunch of iterations with a debugger in a standard programming environment. As soon as your dealing with a sprawling realtime physical system, you can't do that.
I would rewrite this as "Short term focus is pretty standard for those not making the product."
From everywhere I've worked, the more actual work a person is doing on a product, the better they want to make it, and the less they want to deal with architecture problems down the road. The short term morons are always the ones that aren't actually making anything.
If these police are flagrantly ignoring the law, and are getting their news media from conspiracy theorists, they lose the credibility to be trusted in making rational decisions. You don't put people who aren't critical thinkers in positions of extreme power and responsibility.