Why is the first mention of the specific "galaxy next door" (the Large Magellanic Cloud) at the bottom of the summary?

This is supposed to be news for nerds. We know what the Large Magellanic Cloud is. Meanwhile the "summary" buries this information further in its text than TFA!

This isn't the issue. Neo4j didn't violate FSF's copyright.

You distribute your top level license that includes the original text of AGPL alongside some additional restrictions. This is a 100% expected thing to do. The original license has in section 7 a permitted set of restrictions, and then a clause saying that if you find any other "further restrictions" you can strip them out.

The problem is that Neo4j actually did that -- they added an "other further restriction", and someone went and distributed a version with the restriction stripped out as the license says they are allowed to do.

Neo4j could have distributed a version of AGPL with section 7 modified -- but then they actually would be violating the copyright on AGPL. Alternatively they could have written their own license, but then they'd have to pay lawyers to write a proper license that properly expresses what they want which is tricky/expensive to get right.

Do these random contracts have specific language in them saying you aren't allowed to distribute modified copies of their text?

It's one thing to fair use handwave-as-conventionally-accepted only-copyright-violation-in-a-hypertechnical-sense copying text of random licenses and contracts, but a typical conventional contract or license doesn't specifically ask you not to distribute modified copies of it.

It isn't that creative. You've been given a license that has a certain set of terms, one of which says that you're allowed to ignore additional attached terms.

This is ultimately a copyright issue -- of the license itself. FSF doesn't want their licenses used for non Free Software contexts, which is why you are only allowed to distribute the license unmodified and said license text is poisoned against trying to attach additional stuff to it.

From the point of view of FSF this wouldn't primarily be about anything involving Neo4j licensing -- at the end of the day, assuming they own copyright on any relevant code and aren't relying on (A)GPL to have a valid license to distribute a derivative work of other (A)GPL work, they're allowed to write their own license with whatever text they want. The question here is whether people are allowed to rip off the FSF's license texts to license their nonfree software.

While that is largely true, there are definitely scenarios that get more complicated notably if the account holder is actually owed money. There's an extremely relevant issue (mentioned in TFA) with Revlon loans back in 2020. Citi was acting as the agent for a loan to bankrupt Revlon and accidentally credited the creditors accounts for the full value of the lown with the bank's own money, which started a two year legal dispute which would have been entirely avoided if Citi had just not accidentally credited the accounts.

You're complaining about Cruise. Cruise is dead. They had their license pulled in no small part due to the exact incident you're complaining about.

Now that Cruise is gone, the level of newsworthy driverless car badness has dropped from accelerating into pedestrians down to things like getting into honking matches at 4am and spending 5 minutes driving around in circles.

My understanding is that CrowdStrike has (among others) a rollout process specifically designed to address immediate active threats. This rollout is ultimately owned by CrowdStrike as part of their product.

The problem is that they didn't have a testing process even close to being commensurate with that extreme of a rollout -- "roll out everywhere now!" is incredibly dangerous, even (especially!) for updates that are only "configuration", and while they did have some automated testing those tests didn't include actually pushing the update to real machines and making sure it could be rolled back and didn't immediately crash.

I don't think there's anything inherently wrong with it being "a single day" -- there are legitimate tradeoffs with security here that want unusually fast rollouts.

Even still, if this thing had been rolled out over even a couple of hours, even with the crudest of telemetry, it would have presumably been stopped when it only crashlooped a few percent of machines. That still would have been a huge annoyance but it wouldn't have been stop-the-business bad for the large majority of affected businesses.

From what I can tell there are a remarkable number of people who appear to be grinding bullshit culture war axes rather than engaging in things like reading comprehension.

It's not that things haven't always been bad, but it feels like half the posts here the people aren't even reading the posts they're responding to.

The problem is that Weibo has approximately zero market share outside of the Sinophone sphere, and as far as I can tell it has no real interest in changing that.

It is hard to call something an "alternative platform to Twitter" if even basic documentation like the "registration help" links on their signup page are only in Chinese. Meanwhile you can't get serious penetration in China as a media platform unless you get the buy-in of the Chinese government. The net result is that these platforms aren't even in real competition with one another.

The Snowden slide deck on PRISM is over a decade old, and my expectation is that all of those providers that are still relevant have fixed the issues in question.

Uranium just isn't that scarce, given its very high energy density. That is especially the case when you start requiring designs that work for non-fissile fuel.

Broadly speaking the designs that work for 0% fissile Thorium will also work for the 99.3% U-238. The only thing for which there's any scarcity at all is U-235, but even then the fuel is cheap compared to all the other costs of power production)

(There is a legitimate issue that these designs require more highly enriched uranium -- that's a tradeoff to allow smaller scale designs. SMRs are suboptimal for bulk power production in general, but that market is long term going to renewables anyway.)

But this isn't some fundamental restriction. There isn't some magic reason that only Russia can make HALEU. It isn't like Russia is sitting on giant natural HALEU fields that go through HALEU pipelines through the Baltic sea to keep Germany warm during the winter.

HALEU production is an industrial process, and that industry can be built anywhere as needed. There's no large scale HALEU production in the west because there's no demand for it yet, but uranium enrichment is a well understood process.

(There is, of course, proliferation concern as with any sort of enrichment.)

That's an interesting thought.

One of the key points with particle/wave duality is that at higher energies these wavy things become a lot more particle-like. That's why you don't see a fastball showing weird quantum effects -- the wavelength of a fastball (considered as a single object) is miniscule.

Achieving a "superposition of less extreme electormagnetic waves" in this context would have the same level of difficulty as achieving a superposition of fastballs.

I would expect this one to be fairly mild -- it's entirely conceivable that this is a microcode bug to begin with and the fix would be approximately zero cost. At worst I'd expect the cost to be disabling the FSRM optimization.