1,531 karma · joined October 12, 2011
But as a security guy, given the power of Public Key assignment in the context of a system for managing access to Git repositories, I can't help but be a little surprised that model objects that touch Public Keys weren't more thoroughly reviewed.
If nothing else, folks everywhere will be thinking a little harder about authorization logic this week.
With that said, the only real way to fight back against crazy EULAs is to stop using services that have them.
With that said, pick your battles. I'm not a Pinterest user but this EULA wouldn't stop me.
So that's already pretty weak, but then we find out it's implemented with a shared Windows folder.
sigh.
The fact that taxes are collected under threat of force is the entire basis for the objection. Any "funded" work of art, absent the use of stolen money, is by definition an artwork that someone would pay for.
The next time someone takes money from you at gunpoint, be sure to ask them whether they're doing so "to amortize the risk of finding the next Warhol or Banksy." One can hope, right?
Because the funding comes from people who pay it under threat of force. Therefore, "not provably unwanted" shouldn't be the bar.
Fair enough, but that distinction only makes a real difference if the NEA commonly does "last mile" funding (the last 5-20% to reach a threshold of viability, say). Is that the case?
> No one would pay enough to build a nice mural or sculpture in a poor neighborhood, but that doesn't mean it isn't worth doing.
1. The fact that someone has not yet paid, by some date, to build a nice mural or sculpture in some particular poor neighborhood, is not a proof that no one would pay to do so.
2. When I have participated in such projects, they were municipally funded in addition to neighborhood donations of time and materials, and I doubt any expenses were recouped from some NEA "hood aid" package.
3. If you think it's worth doing, do it.
> The straightforward corrolary to what you wrote is that the artistic desires of the wealthy are inherently more valuable
Artistic desire is a universal to which all humans are entitled. The power to commission other people of talent to create physical manifestations of my artistic desire is something I am only entitled to if I can afford to pay those people for their time and materials.
Many would argue that "taking taxpayer money to fund something that no one would pay for" is a coherent definition for "public disservice."
If you form all of your opinions worrying about all the idiots or evil people who might happen to agree with you, or use your arguments to further their own nefarious ends, you're destined to lead a very quiet life.
> ICE proved itself. ICE isn't on trial here.
The usability and cost/benefit of electric drivetrains versus the status quo is relevant. My point was not "we should distrust ICE," so much as "we should discuss cost/benefit tradeoffs of technology like reasonable people instead of resorting to ZOMG BRICKING".
Which, for many drivers, may as well be $40k.
> the solution is a combination of educating/warning owners & notifying them by phone or email if the car starts to get too low
I never advocated ignoring anything. My point is not that "Tesla is great" or "boo ICE yay electric," it's that all the hysteria around "OMG car bricking" doesn't actually promote whatever communication/engineering solutions would actually make the product better or more consumable for people.
In the ICE case, X is "maintain a minimum oil level while the engine is running." In the Tesla case, it's "maintain a minimum battery level, even during storage."
Given that the underlying drivetrain technologies actually are worlds-of-difference apart from each other, that strikes me as a pretty minimal difference in terms of routine maintenance. Unless it's somehow difficult to understand or costly to implement, we should assume Tesla customers aren't f'ing morons and go about our business.
You can't blame the lobbyists' lawyers for trying to enforce a provision that their clients successfully negotiated. You should be ripshit that they were able to negotiate the provision in the first place.
There are any number of easy ways to 'brick' an internal combustion engine, and yet we're not all torches 'n' pitchforks over them. Partially because ICEs have been around so long that the relatively short list of "things to avoid" is burned indelibly into the popular consciousness. Partially because over a hundred-odd years of continuous engineering, a typical ICE can take a hell of a lot of abuse before it fails.
And note that the "shit that might happen to you" column still isn't trivially dismissed on the ICE side, even after 100+ years of safety engineering. We physically pump highly-flammable liquids into our gas tasks; people still occasionally get burned or even die doing that shit!
Couldn't find many stats, but this is interesting: http://www.nfpa.org/assets/files/PDF/Research/FireSafetyVehi...
Let's assume the $40k figure is at all likely for a vehicle owner that RTFM'd. I'm pretty sure anyone ever burned in a gas-fueled vehicle fire would gladly go back in time to fork over $40k to avoid that experience.
Unless it's the case that it actually costs Amazon money to offer books at the prices that IPG wants, this is a pure power/spite/warning play. And I very much doubt that it costs them money.
They need a Security story other than "run it on an appliance inside your network." I would also appreciate a single page (unless I missed it) that explains the Analysis value-adds.
* == "at location"
& == "the address of"
There are cases where this doesn't work well (or at all), but it works for many of the cases that initially look like jibberish to a C noob.
For declarations, just put variables on separate lines.
Here's hoping the installer either a) checks actual machine specs rather than machine "version number") (not likely), or b) can be cajoled (annoying).