If you think Meta doesn't already censor accounts all over the world on behalf of the United States, I have a space elevator to sell you. For example, make an off-hand comment about how easily Canada could manufacture a dirty bomb as protection against US aggression and watch limitations start to be applied to your activities. Meanwhile, Russian bot pages continue to be treated as honoured guests.

no problem.

Not just Kafka, but also stream processing of Kafka originated data.

We use it to run a cities public transit realtime data system (track vehicles, display information on realtime maps, public information displays, make predictions), and it works well - there are features which I think are snake oil (schema registry for example), but its been rock solid, performant, and the UI is decent.

Keeping people employed just because is probably the reason the USPS is having the issues it already has. Cutting the workforce and cutting every other day of delivery could make a HUGE impact to their bottom line. Likely the same mail trucks could carry and deliver two days of mail every other day without needing to put more trucks on the road.

No, the USPS is having to fully fund pensions for people not born yet is what's causing the problems. If you look at the profitability graph it nosedives around year 2000 or so purely because Bush Jr and the GOP were trying to kill it by forcing it to fully fund pensions for the next 75 years or so, which includes funding pensions for people not born nor employed by the USPS.

Most companies aren't doing this which means if they go under, there goes all the pension funds. USPS pensions being fully funded means those people keep their funds when USPS goes under.

It's basically been a way to kill the USPS without killing the USPS directly.

Before this ruling came out, the USPS was really quite profitable, and those profits could've been used to fund the pensions until the obligation was met rather than force them to pay for pensions fully by going into debt.

I'm actually responding to the AC above you. He is arguing that the attack wouldn't make any sense for either country to make, based on *national* interest. I'm pointing out that's not the only framework in which *regimes* make decisions.

The other problem with biodiesel is there isn't enough of it. The only reason it works right now is few people are converting used oils to biodiesel for their own private purposes. If you're doing it at an industrial level there just isn't enough feed stock available.

And it doesn't work too well in cold environments - you have to start the engine using regular diesel because biodiesel when cold is basically a cold gloopy fat blob and needs regular diesel to be thinned out.

Hardly. There's no memory manufacturers in any way restricting production to "manufacture this shortage". They may be price fixing (they have a history of that) but right now they are producing memory at full tilt.

And if you ask why they didn't invest years ago, can you please tell me tonight's winning lotto numbers since you are so good at predicting the future?

They are also not increasing production - because the past decade they've done so and gotten screwed over - prices spike, they increase production and then demand collapses, leaving a huge oversupply of RAM and them having to dump it for low prices. So they aren't producing anymore memory than they normally could.

Instead they're switching production to things like HBM needed for the AI chips and such.

How do you know that?

Being from Google, I rather assume the opposite - and that they probably focused their engineering effort to make sure the reduced battery life didn't give their corporate surveillance activities away.

I'll find out in mid January, lol - it's en route on the Ever Acme, with a transfer at Rotterdam. ;) But given our high local prices, it's the same cost to me of like 60kg of local filament, so so long as the odds of it being good are better than 1 in 8, I come out ahead, and I like those odds ;)

That said, I have no reason to think that it won't be. Yasin isn't a well known brand, but a lot of other brands (for example Hatchbox) often use white-label Yasin as their own. And everything I've seen about their op looks quite professional.

You needed a handbook for that?

Anyone who ever went to a business meeting could've told you that.

By my experience, it takes only 4 things to make a meeting productive: a) someone is in charge of the meeting and moderation, b) that someone had time to prepare, c) everyone in the meeting has received an agenda with enough lead time to have read it and (if necessary) prepare their part, at least a bit and finally d) there is at least a simple protocol of the meeting for those who couldn't attend, those who dozed off in the middle, and those who claim next week that something else was agreed on.

Uh oh, someone poked a panda bear.

Correct.

Big screen and big sound. Maybe it doesn't mean much because you have a house in the suburbs, but if you're in an apartment (either because you don't want to commute, you want to live in a city, or it's all you can afford for housing), TV speakers are pretty much it because anything more will get you noise complaints.

Depending on your income and housing costs, you may be limited on how big a TV you can have as well.

So a theatre is pretty much the only place if you want that sort of thing.

Granted, I don't go out to theatres much anymore either - and I spent $35 on the ticket (one, for myself), mostly because I want the big screen IMAX, but it's a far drive. And the local theatres are regular screens which aren't great. I pretty much limit myself to one movie a year or so tops.

I believe part of the reason is the year 2038 issue. A while ago I remember seeing posts about the issues FreeBSD has/had with getting around 2038 on their system. IIRC, it was a huge effort.

*EVERY* UNIX and UNIX-like system has to deal with the problem. But it's got nothing to do with 32-bit systems, because OpenBSD and NetBSD have it working since 2012 on 32-bit systems. Linux since 2020 (Linux supported 64-bit time_t on 64-bit platforms already, but 2020 is when 32-bit systems supported it).

It's not a simple solution, but it's been done before on other systems. It's also why Linux has a bunch of system calls that are merely using 64-bit versions.

Just put it in context: Today Russia struck the Pechenihy Reservoir dam in Kharkiv.
Russia launched the war because they thought it would be a quick and easy win, a step towards reestablishing a Russian empire and sphere of influence, because Putin thinks in 19th century terms. Russia is continuing the war, not because it's good for Russia. I'd argue that winning and then having to rebuild and pacify Ukraine would be a catastrophe. Russia is continuing the war because *losing* the war would be catastrophic for the *regime*. It's not that they want to win a smoldering ruin, it's that winning a smoldering ruin is more favorable to them and losing an intact country.