The first stage of the revolution is to keep a cordial relationship with the Mensheviks. We're all on the same team. We're hear to overthrow that rotting edifice of the old order and create a stronger, better society, with a government truly representative of the people. We're all a big tent, and can accommodate differences of opinion.

The second stage of the revolution requires the sidelining of the Mensheviks. Yes, they have their objections, but those objections are mainly spurious, perhaps a little too influenced by moderate opinions. It's understandable, revolutions have casualties, and not everyone has the stomach for the hard fight. Objections will be duly noted and recorded.

The third stage of the revolution requires the expulsion of the Mensheviks. They've become too influenced by counterrevolutionary ideas. The middle ground they try to occupy is the path back to the old order. The revolution cannot afford these divisions, the people must see unity lest they question the revolution. Show the counterrevolutionaries the door, we no longer recognize their standing.

The fourth stage requires the destruction of the Mensheviks. It is not enough that they have been rendered impotent, they are traitors to the revolution, and like the moderates, in the hands of the old order. Some, maybe, can be rehabilitated, others must face more severe punishments. We owe to the people to destroy those who would undo our accomplishments.

The fifth stage has no memory of the Mensheviks at all.

I think you need to provide your operating definitions for "socialism" and "communism".

Rather ironic that the real Communists are the Republicans.

I've been busily installing Debian on our Windows 10 machines. A few little hiccups here and there, but all in all, it's working like a dream.

The only Windows I use is the Server 2016 RDP managed service my company pays for, so updates are invisible to me. My two MacBooks and my Ubuntu laptop all have sane update policies which remind me of updates, without endlessly clogging up the works by downloading the updates. Every time I use an actual Windows machine I'm reminded of what an appallingly bothersome workflow-interrupting OS it has become.

It is literally a summarization model. Its context window is the text to summarize. It was literally trained on being given text as a context, and summaries as outputs.

Yup. I remember going to an IBM seminar around 1994 or 1995 where they demonstrated a new IDE environment that was going to end traditional programming. They gave a demo of writing some sort of simple application with input, with a library of GUI windows connected via some sort of flow chart. At the time I thought "Fuck me, I'm out of a job", but I never really saw the product again (for some reason I think it used Smalltalk, but it has been thirty years) and when I started using visual tools, it definitely wasn't the connect-a-dot that everyone claimed.

Worse, the stuff that was connect-a-dot, like all those horrible MS-Access applications written with Visual Basic, or the insane Excel sheets using lookups to make spreadsheets behave like RDBMSs, if RDBMSs had been written by victims of errant brain surgery, my career quickly morphed into a series of contracts in the vein of "Please fix the awful system we built in-house and we run all our Accounts Receivable through, but the guy who maintained it got hit by a bus."

(Which isn't actually much of an exaggeration, I had to take over a PHP project that had been half written by a guy who got some sort of serious illness, was taken over by some other guy who had no idea what he was doing, and the company had already sunk $40k into).

AI Overview literally tells you what sources it's drawing on. I don't see why people are capable of looking at what the sources are when they're Google search answers but not when they're AI Overview source links, but apparently, that is hard for some people.

This. Most people inevitably respond in these threads talking about "the model's training". AI Overview isn't like something like ChatGPT. It's a minuscule summarization model. It's not tasked to "know" anything - it's only tasked to sum up what the top search results say. In the case of the "glue on pizza" thing, one of the top search results was an old Reddit thread where a troll advised that. AI overview literally tells you what links it's drawing on.

Don't get me wrong, there's still many reasons why AI overview is a terrible idea.

1) It does nothing to assess for trolling. AI models absolutely can do that, they just have not.
2) It does nothing to assess for misinfo. AI models absolutely can do that, they just have not.
3) It does nothing to assess for scams. AI models absolutely can do that, they just have not.

And the reason the have not is that they need to run AI Overview hundreds of thousands of times per second, so they want the most absolutely barebones lightweight model imaginable. You could run their model on a cell phone it's so small.

Bad information on the internet is the main source of errors, like 95% of them. But there are two other types of mistakes as well:

4) The model isn't reading web pages in the same way that humans see them, and this can lead to misinterpreted information. For example, perhaps when rendered, there's a headline "Rape charges filed against local man", and below it a photo of a press conference with a caption "District Attorney John Smith", and then below that an article about the charges without mentioning the man's name. The model might get fed: "Rape charges filed against local man District Attorney John Smith", and report John Smith as a sex offender.

5) The model might well just screw up in its summarization. It is, after all, as miniscule as possible.

I personally find deploying a model with these weaknesses to be a fundamentally stupid idea. You *have* to assess sources, you *can't* have a nontrivial error rate in summarizations, etc. Otherwise you're just creating annoyance and net harm. But it's also important for people to understand what the errors actually are. None of these errors have anything to do with "what's in the model's training data". The model's training data is just random pieces of text followed by summaries of said text.

I guess I would be more excited if I hadn't abandoned Windows on my own personal devices (still have to use it via RDP at work). I think the Wine project has done an incredible thing, I just don't have any particular use for it anymore.

Almost as bad as a non-existent succession plan is a succession plan even the successor knows nothing about. If Linus has a successor, that successor should be well aware, and already be a contributor to that succession plan. This isn't a will where you're pleasantly surprised your rich great-uncle left you his house on the French Riviera, this is a major project that is an integral component of thousands of technologies and workflows.

Neutrinos are called ghost particles because of how little they interact with other matter. They're constantly streaming through your body without interacting with you. A solar neutrino passing through the entire Earth has less than 1 in a million odds of interacting with the Earth.

Not like this with this - the energy here equates to a couple hundredths of a joule. Now, the "Oh My God! Particle" had a much higher energy, about three orders of magnitude higher. That's knock-photos-over sort of energy (and a lot more than that). The problem is that you can't deposit it all at once. A ton of energy does get transferred during the first collision, but it's ejecting whatever it hit out of whatever it was in as a shower of relativistic particles that - like the original particle - tend to travel a long distance between interactions. Whatever particle was hit is not pulling the whole target with it, it's just buggering off as a ghostly energy spray. There will be some limited chains of secondary interactions transferring more kinetic energy, but not "knock pictures over" levels of energy transferred.

Also, here on the surface you're very unlikely to get the original collision; collisions with the atmosphere can spread the resultant spray of particles out across multiple square kilometers before any of them reaches the surface.

The average ICE car burns its entire mass worth of fuel every year. Up in smoke into our breathing air, gone, no recycling.

The average car on the road lasts about two decades, and is then recycled, with the vast majority of its metals recovered.

The manufacturing phase is not the phase you have to worry about when it comes to transportation.

Any sources for this

Anonymous (2021). "How My Uncle’s Friend’s Mechanic Proved EVs Are Worse." International Journal of Hunches, 5(3), 1-11.

Backyard, B. (2018). "EVs Are Worse Because I Said So: A Robust Analysis." Garage Journal of Automotive Opinions, 3(2), 1-2.

Dunning, K. & Kruger, E. (2019). "Why Everything I Don’t Like Is Actually Bad for the Environment." Confirmation Bias Review, 99(1), 0-0.

Johnson, L. & McFakename, R. (2022). "Carbon Footprint Myths and Why They Sound Convincing After Three Beers." Annals of Bro Science, 7(2), 1337-42.

Lee, H. (2025). "Numbers I Felt Were True". Global Journal of Speculative Engineering, 22(1), 34-38.

Outdated, T. (2015, never revised). "EVs Are Bad Because of That One Study From 2010 I Misinterpreted." Obsolete Science Digest, 30(4), 1-5.

Tinfoil, H. (2020). "Electric Cars Are a Government Plot (And Other Things I Yell at Clouds)." Conspiracy Theories Auto, 5(5), 1-99.

Trustmebro, A. (2019). "The 8-Year Rule: Why It’s Definitely Not Made Up." Vibes-Based Research, 2(3), 69-420.

Wrong, W. (2018). "The Art of Being Loudly Incorrect About Technology." Dunning-Kruger Journal, 1(1), 1-?.