apartheid:
  a policy or system of segregation or discrimination on grounds of race.

Seems like walling off Palestinians would be consistent. Also, you have the West Bank situation, which the ICC/UN, France, UK, EU, and US have all described as a war crime (US temporarily said it wasn't, but switched back in February). In Gaza the objection is the disproportionate response, even though the settlements did stop, but the West Bank still suffers from the settlements and associated forced transfer of property away from Palestinians.

Just because they should realistically expect to put their job at risk doesn't mean they did the "wrong thing". The "disturb the peace" line as a reaction to the concept of protest is a bit disconcerting.

Now if they were being obnoxious in the workspace chanting about injustice against palestine in some totally unrelated venue (e.g. if Google did zero business with Israeli government), I could see scoffing at the effort as noisy and disruptive to no end.

However, they are directly protesting their own companies behavior. Disruptively protesting in the workplace is pretty much exactly what their cause demands in this scenario.

I have grown tired of "there's no wrong way to protest" being spouted when people do incredibly stupid, unjust, or self-harm stuff in the name of "protest", but here it's supremely on point. Then I still see people with "protest somewhere quietly that no one has to hear", which closes off *any* form of protest and demands deference to some folks.

Even the most professional of officers would be tempted if he was was cheating on him or if someone delivered a credible threat to the safety of his children.

The best way to prevent this kind of abuse is to make it impossible.

LK

Edward Snowden showed that this is not as true as you seem to think it is.

LK

Then, let them serve the warrant.

What is different is that for the first time in human history, it's not only possible but it's practical to have encrypted communications that no one can access except for the intended recipient.

All of "the most heinous of crimes" take place in the real world, there is some physical action that can be detected and punished. I don't care if this makes the job of law enforcement harder. I want law enforcement to be a difficult and time consuming job. Idle and bored cops tend to find ways to fill their time and it's never good.

LK

I've been thinking about adding solar panels to my house. I would love if I could get a federal subsidy to do it. However, just like with my student loan forgiveness, I'm NOT giving Biden my vote in exchange.

LK

I can only speculate, but:
-I had heard that the IBM PC effort wasn't exactly fully supported by the wider IBM, so they had to make do and potentially might have had to be willfully overly optimistic to rationalize their plan to have so much of the system defined by freely implementable standards
-They might have hubris that BIOS was 'hard', at least the business leadership I could easily imagine thinking that, and no one is going to second guess them.
-They might have assumed copyright would have protected the interfaces, rather than technical difficulty.

But it wasn't that they were careful not to do damage, they were careful, but the damage was yet to be seen.

I think it's hard to say, as no one can point to a party that would have likely otherwise caught it, except some guy that noticed that ssh session establishment was 'a bit off'. In fact, if his random usage of xz had been a couple weeks later, he probably wouldn't have investigated because the attackers had released a "fix" for the performance impact. This was from all appearances pure luck that this guy happened to have the noticeable xz impact and cared enough to dig in, and did so immediately rather than maybe waiting a couple of weeks and it would have been "fixed". A two week window between the relatively obvious and the fixed version that from what we can tell, *almost* passed without anyone getting suspicious, except for that one guy.

Many eyes worked this time, but *barely*.

so where does that leave us? Does that basically nullify the red shift?
and if so what could we draw from that? Not necessarily that the universe is quite a steady state?

No, the universe is still expanding.
This has been established since Slipher/Hubble in the 1920s or so.

But, if Sarkar is right, then this expansion is NOT accelerating, which was what the 2011 Nobel Prize was awarded for.

And it may resolve the "crisis in cosmology" where the rate of expansion is different when measured using two different phenomena (Cosmic Microwave Background radiation vs. Supernova standard candles).

It also casts doubts on what some aspects of Dark Energy and such.

As I recall, they had enabled everything to be done freely except the BIOS. They thought the BIOS would be a lock on the core platform, but enjoy a rich ecosystem of peripherals and suppliers. When companies cloned the BIOS, they did try to sue. Think it became quickly obvious that clean room cloning of the BIOS was too easy and nothing illegal about that.

That is it in a nutshell ...
And it makes a lot of sense, if the observations are correct.

If his research pans out, then one Nobel Prize was awarded for an erroneous interpretation.

Adam Reiss, Nobel Laureate for that prize criticizes Sarkar's work, but he has a vested interested in the status quo. Other experts should chime in, and more observations and analysis are needed.

It depends on how many people are inclined to agree with them and their relative importance to the mission of the company, which they won't know until they try.

By being fired and it becoming headline news, if a critical mass agree with them it might hurt Google's financials and teach the lesson that there's a business cost associated with that behavior. If that lesson is taught, and enough other suppliers learn the same lesson, it may make things harder for Netanyahu and perhaps a more moderate opponent prevails.

If being fired undermines the quality of the product, and you repeat this through enough suppliers, again, similar outcome, things are harder for IDF and Netanyahu opposition may be able to leverage that to a political victory.

In isolation, sure, the impact of a singular act like this is unlikely to have practical import. However if a critical mass of like minded folks act consistently, then it can effect change.

Don't know if that would have helped.

We see that the central complaint is that Microsoft was upselling "logging capabilities". Question is what, specifically, is he talking about? I wager it's not just logging, I'm sure even Microsoft provides at least those. I suspect it's about some sort of log analysis, since 'analytics' is a favorite upsell opportunity in the industry (Cisco paid $28 billion for Splunk for example).

Whether it's Linux or Microsoft technology, I'm wagering they'd still be complaining about not having adequate log analysis tools.

I suspect they got screwed by SolarWinds, they wanted more budget to mitigate this and got shot down as the headline was SolarWinds screwed up, not that Microsoft wouldn't include log analysis, and are pivoting to trying to embarass Microsoft into making those offerings included in the base tier.

Well, he's right here. This was an individual who happened to stumble into this who happened to be employed by Microsoft.

There's plenty to point to to suggest that Microsoft isn't worse than some competitors that people might suggest or even better in some regards, but the XZ situation has nothing to do with Microsoft technical or business leadership other than happenstance of employing the one guy.

Since the thread is about the XZ issue, this is an odd statement to make. They weren't careful, they got caught before it hit widespread deployment. It had barely been in a tagged xz release and only barely made it into the bleeding edge rolling test releases of select distributions. We have no information on what they would have done if it had lived long enough to be in widely deployed Ubuntu LTS, RHEL, SuSE, embedded implementations.

Funnily enough, they might have been foiled anyway, because at the same time, systemd was looking to stop linking to various external libraries including XZ, to reduce bloat. So even a systemd-patched OpenSSH still wouldn't have linked to XZ or load XZ ever if that change got folded in before XZ had a chance to inflict the attack.