jml7c5

Those aren't really relevant to the topic of Chinese ownership, unless you believe the government told TikTok to actively promote those videos. The stupid destruction trends seem organic to me, and did not require CCP interference.

My partner and I were consumed by this for a while. There's something very satisfying about hopping from cluster to cluster and recognizing the various meanings of a word.

Makes me wonder what 3D (or even 4D) version would be like.

Yes, it's all unified memory.

As much as I dislike the loss of socketed RAM, I have to say it's working out well for Apple users so far. I wonder if CXL will change the situation for consumer devices or if it will only be useful at the scale of a server rack.

Are you using flakes? AFAIK `command-not-found` does not work with them. See https://github.com/NixOS/nixpkgs/issues/171054 and https://discourse.nixos.org/t/why-isnt-there-an-official-bui...

`nix-index` is a flake-compatible alternative: https://github.com/bennofs/nix-index

Though it says "chat-by-chat basis", which sounds like individual user action.

It is remarkable. When Her was released I was uninterested in seeing it ― despite glowing reviews ― because it seemed implausible that any believable, conversational AI would arrive in a near future setting. When I saw the trailer it felt to me like someone with little technical knowledge had seen Alexa, Siri, etc and extrapolated a silly future, much as science fiction in the 60s and 70s imagined people of the 2000s donning bubble helmets and casually taking vacations on the moon. And yet here we are today with LLMs (which many don't even see as a route to AGI!) expressing all of this unexpectedly complex behavior.

>You are decades out of touch with reality, because I read years ago already that some guys estimated we hit the break even point (in the "western world") in the mid 90s already.

And you are out of touch with the current reality. The "western world" is currently undergoing a labor shortage; in the United States, unemployment just hit its lowest point in 50 years! That runs completely counter to the thesis that increased automation will inevitably cause mass unemployent.

You've also disregarded the obvious solution to any decreasing demand for labor: make the work week shorter and everyone simply works fewer hours.

>The more we automate all these things, the less humans are involved, and following that it means the economy will shrink.

You've conflated "the size of the economy" and "total hours of labor". By any reasonable definition of economic size, if you have two societies and one produces more economically valuable output than the other, then it is larger, regardless of how many hours of labor are involved. One worker with a spoon produces less than one worker with a shovel, and spending ten times as long to achieve the same result does not make that economy larger.

This quote is relevant:

>The make-work bias is best illustrated by a story, perhaps apocryphal, of an economist who visits China under Mao Zedong. He sees hundreds of workers building a dam with shovels. He asks: “Why don’t they use a mechanical digger?” “That would put people out of work,” replies the foreman. “Oh,” says the economist, “I thought you were making a dam. If it’s jobs you want, take away their shovels and give them spoons.”

I think you are wrong in saying "Basic income needs to happen first." [emphasis mine] We have continually increased efficiency for hundreds of years without causing mass unemployment. I think there's still quite a ways to go before we have more bodies than we can find a use for. Not to mention there's a shorter, 32-hour week on the horizon that could negate the effect of less demand for labor.

I've found that simply lowering maximum fan speed on my laptop works well. The fan on what I'm using is nearly inaudible at 30%, yet I still get 90% of the performance on long-running tasks. Much as with desktop CPUs, you pay a lot for that last 10%.

On that note, a lot of laptops have goofy fan curves. In theory, you want the fan to move just enough air that the CPU doesn't throttle, since the rate of heat transfer is proportional to the heatsink-to-air temperature difference.

Weren't there only four witnesses? The pilots were the only ones who saw anything with their own eyes. And there's been no release of sensor data or video, so it's hard to judge its quality. (The 'FLIR1' video was taken later, by different pilots who did not see their object visually, and simply shows a distant hot object slowly moving left, with no inexplicable manoeuvers.) That the ship radar was purportedly bouncing between maximum altitude and reasonable altitude suggests a software or hardware issue, or electronic interference.

-77.7 ºC, for those wondering.

Does it save each tab's back/forward history? AFAIK, the WebExtension API doesn't provide any robust mechanism to obtain it directly.

It's silly, but I wish the HD aspect ratio had been the golden ratio. There's something very satisfying about it, even if its properties would be of little practical use. (Though I wouldn't have minded the extra vertical space!)

Perhaps "once we have imported your data, you can quickly retrieve data from the cloud using the regular S3 APIs and fee structure". Or in other words, "there is no special restriction on data added through Snowball".

Feels a bit like intentional misdirection, but it's more likely a case of sloppy writing.

Foone stopped posting on Twitter shortly after Musk bought it. They're over on Mastodon now: https://digipres.club/@foone

It's a Cessna rather than a commercial airliner, but slamming a plane into landmark buildings was not tabo or out of the ordinary pre-9/11: https://youtu.be/ssig3LUCwng?t=4m35s.

It is a sort of coincidence that Apple decided the pinky finger button should be control rather than command. The other way around and crouch-jumping would be more difficult and you'd want to rebind it... but you would then run into the same keybind overlap issue as experienced on Windows/Linux.

There's no need for italics; the parent post already acknowledges Graeber's death.

At this early stage, filtering for misogyny may just be easier. My guess is that filters for misandry may give too many false positives.

Bit flips aren't evenly distributed over time or across RAM. In other words, the vast, vast majority of DIMMs are good and will never have a bit flip. For those modules, the money you spent on ECC will be in a sense "wasted". (Except for the value of knowing that you had a good module in the first place.)

Do any review sites do multiple benchmarks at more than a few different power limits? I'd love to see a graph of power limit vs benchmark result for any given CPU.

My only objection to on-die ECC is that, AFAIK, there's no way to query the number of internal corrections that have occurred. That is important information! Yes, it might freak out some sysadmins that frequent corrected errors are now "normal" (after all, the main reason for on-die ECC is that manufacturers won't have to scrap slightly imperfect DRAM), but those individuals can be re-educated, and I really want to be able to tell if a given module is running within spec yet right at the edge of failure.

In related news, libinput is almost ready to merge customizable pointer acceleration curves: https://gitlab.freedesktop.org/libinput/libinput/-/issues/35...

Might not be so bad even if that solution doesn't work. We got oats and rye out of it last time around: https://en.wikipedia.org/wiki/Vavilovian_mimicry

I found it extremely helpful to first study the basic physics of electromagnetism in some depth rather than jump straight to electric circuits and components. Any undergrad physics textbook that eventually teaches Maxwell's equations will do. For video format, Walter Lewin's 802.x MIT lectures are freely available online. (I think there's some debate over whether he got a particular example involving Kirchoff's Law quite right. Not sure what other lecturers are good, but they are around if you find Lewin not to your liking.)

I hope it isn't a real thing! I was being facetious.

"All is fair in Love and Civ" is a common variant of the default rules. It introduces the "your box has been pwned" victory/loss condition.

Do you use a userspace OOM killer, like oomd or systemd-oomd?

It's worth noting that they primarily pursue this as a pleasurable puzzle, not for any practical payoff to the problem of player primacy:

>We both understood that this was really a "solution looking for a problem" (there are plenty of perfectly acceptable ways to quickly determine who might go first in a game), but mathematically, wouldn't it be great if a set of dice could be created [...]

Thank you!