I wouldn't be surprised to if this was largely accounted for in supply side contamination issues. It appears that Amazon treats all SKUs identically, sourcing the closest one to fulfill and order, regardless of how that SKU arrived at Amazon.
A concrete example: No Starch Press customers are receiving counterfeit books when ordered from No Starch Press' Amazon store.
Even if this scam is caught, it's still cost Amazon money in dealing with the issue. (And cost legitimate vendors no end of frustration with legitimate customers receiving fake books.)
"Stand your ground" laws just mean there is no duty(law) to seek retreat above all else before actively defending yourself.
"Castle", in California, simply means that if an intruder has bypassed a control (picked a lock, broke a window, etc) to gain entry then one can proceed on the assumption that they are there to do grave bodily harm. (And thus act accordingly.)
Close... they require the person standing-ground to perceive a threat. The laws do vary state-by-state, but they tend to be universally broad.
"For example, Michigan's stand-your-ground law, MCL 780.972, provides that "[a]n individual who has not or is not engaged in the commission of a crime at the time he or she uses deadly force may use deadly force against another individual anywhere he or she has the legal right to be with no duty to retreat if ... [t]he individual honestly and reasonably believes that the use of deadly force is necessary to prevent" the imminent death, great bodily harm, or sexual assault of himself or another individual."
According to this, if I thought someone was a habitual sex offender, I think I'd be within my right to sniper him from a mile off... so... clearly that's a stretch... but it has been stretched pretty thin before.
> It’s not that he wanted to shoot the intruders next door, he said, “but if I go out there to see what the hell’s going on, what choice am I going to have?” The dispatcher told him again to wait for the police, not to go outside with his shotgun, that nobody needed to die for stealing.
> Horn was unconvinced. “The laws have been changed…since September the first, and I have a right to protect myself,” Horn said. “I ain’t gonna let them get away with this shit. I’m sorry, this ain’t right, buddy … They got a bag of loot … Here it goes buddy, you hear the shotgun clicking and I’m going.”
> “Move, you’re dead,” he told the men, then he fired three times, killing both men, and returned to the phone in his house.
> “I had no choice, they came in the front yard with me, man, I had no choice,” he told the dispatcher. Police arrived seconds later. Horn wasn’t arrested, nor was he indicted by a grand jury that later considered the case.
Excepting that in SF the "everyone" does not want the land owners to make productive use of it: they want the status quo. (Well, the status quo of what the remember as being the "high point".)
Having witnessed protests that occurred midway through the reconstruction of offramps, (meaning an existing ramp was torn down, and they were half done rebuilding it), it's not so much NIMBY, but NBAA: Never Build Anything, Anywhere.
The only way that higher taxes would be beneficial is if SF landowners were actually allowed the freedom to upgrade their properties. Zoning, especially height restrictions (40' max over most of SF), as well as endless red tape, make it really hard to make productive use of prime land. Regardless if it's the original owner or new buyer.
( A new buyer is granted some slight advantage, but not enough to be meaningful.)
One also needs to take into account how these larger companies' internal groups function.
"Brian" probably looked into it, knowing that obscurity != security, but got a response back from the group responsible that was the way they intended it to work, and that group's management wasn't going to do anything about it. "Brian" may have even put messages in the right ear up the management chain such that it would actually effect the outcome.
The fact that the email exchange lasted 2 months before "Brian" said "Sorry, not a case." probably means that "Brian" was trying to make it happen and had actually done an analysis.
* Note: I'm NOT Brian. I've never worked for Microsoft.
Probably some metric says that if "Bob" gets less than X cases per year he gets a bonus. Problem is "Bob" determines "Frank's" wage and "Frank" is "Brian's" boss. It is probably more complicated than that but that's what it always boils down to.
"""Micro was a way of creating a foundation for writing and running distributed systems. It's a pluggable architecture so that the underlying systems can be swapped out based on preference."""
At what point do we just admit that we've re-invented the large co-ordination frameworks of years past? Like CORBA?
Is it the point where we add a JSON schema validator? or switch to Protocol Buffers or some variant?
I think those who've been doing this for a while joke about it all the time. I know I do. I and many others have no illusions about the cyclical nature of technology. It's just that at certain points in time we've tried certain methods and they just weren't the right fit or bastardised to a point of becoming more of a problem. So we try again, lo and behold, we start to get somewhere with it.
Moving to a distributed system is inevitable when you want to scale. We make certain tradeoffs doing it. Over the next couple of decades we'll see some cycles happen again where monoliths are cool again and then distributed systems come back into fashion. Just the way it goes.
"""One of the terrorists pulled out a laptop, propping it open against the wall, said the 40-year-old woman. When the laptop powered on, she saw a line of gibberish across the screen: “It was bizarre — he was looking at a bunch of lines, like lines of code. There was no image, no Internet,” she said. Her description matches the look of certain encryption software, which ISIS claims to have used during the Paris attacks. """
Possible explanations:
1. POST
2. Linux
3. Elm/Pine/Mutt
There are enough hints in her description that the woman they talked to would be 100% content with an OS that booted directly to the browser, and furthermore, she wouldn't know the difference.
The issue is that it needs to be explained in terms that they can understand: ... or part of your line will fail, randomly, and may take over a day to repair, IF your maintenance procedures are current, if not, you'll lose 4-5 days of line time.
Note: not one mention of "security", or good neighbor, or infection, only cutting to the point.
