Of course, another option is for people to dramatically curb their use of social media, or at a minimum, regularly delete posts after a set time threshold.

Deletion won’t deal with someone seriously-interested in harvesting stuff, because they can log it as it becomes available. And curbing use isn’t ideal.

I mentioned before the possibility of poisoning data, like, sporadically adding some incorrect information about oneself into one’s comments. Ideally something that doesn’t impact the meaning of the comments, but would cause a computer to associate one with someone else.

There are some other issues. My guess is that it’s probably possible to fingerprint someone to a substantial degree by the phrasing that they use. One mole in the counterintelligence portion of the FBI, Robert Hanssen, was found because on two occasions he used the unusual phrase “the purple-pissing Japanese”.

FBI investigators later made progress during an operation where they paid disaffected Russian intelligence officers to deliver information on moles. They paid $7 million to KGB agent Aleksander Shcherbakov[48] who had access to a file on “B”. While it did not contain Hanssen’s name, among the information was an audiotape of a July 21, 1986, conversation between “B” and KGB agent Aleksander Fefelov.[49] FBI agent Michael Waguespack recognized the voice in the tape, but could not remember who it was from. Rifling through the rest of the files, they found notes of the mole using a quote from George S. Patton’s speech to the Third Army about “the purple-pissing Japanese”.[50] FBI analyst Bob King remembered Hanssen using that same quote. Waguespack listened to the tape again and recognized the voice as Hanssen’s. With the mole finally identified, locations, dates, and cases were matched with Hanssen’s activities during the period. Two fingerprints collected from a trash bag in the file were analyzed and proved to be Hanssen’s.[51][52][53]

That might be defeated by passing text through something like an LLM to rewrite it. So, for example, to take a snippet of my above comment:

Respond with the following text rephrased sentence by sentence, concisely written as a British computer scientist might write it:

Deletion won’t deal with someone seriously-interested in harvesting stuff, because they can log it as it becomes available. And curbing use isn’t ideal.

I mentioned before the possibility of poisoning data, like, sporadically adding some incorrect information about oneself into one’s comments. Ideally something that doesn’t impact the meaning of the comments, but would cause a computer to associate one with someone else.

I get:

The deletion of data alone will not prevent a determined party from gathering information, as they may simply record the information as it becomes available prior to its deletion. Moreover, restricting usage is not an ideal solution to the problem at hand.

I previously mentioned the possibility of introducing deliberate errors or misinformation into one’s own data, such as periodically inserting inaccurate details about oneself within comments. The goal would be to include information that does not significantly alter the meaning of the comment, but which would cause automated systems to incorrectly associate that individual with another person.

That might work. One would have to check the comment to make sure that it doesn’t mangle the thing to the point that it is incorrect, but it might defeat profiling based on phrasing peculiarities of a given person, especially if many users used a similar “profile” for comment re-writing.

A second problem is that one’s interests are probably something of a fingerprint. It might be possible to use separate accounts related to separate interests — for example, instead of having one account, having an account per community or similar. That does undermine the ability to use reputation generated elsewhere (“Oh, user X has been providing helpful information for five years over in community X, so they’re likely to also be doing so in community Y”), which kind of degrades online communities, but it’s better than just dropping pseudonymity and going 4chan-style fully anonymous and completely losing reputation.

I imagine it’s rephrased “Copilot”.

the resulting error messages normally at least give you something to search for

lp0 on fire

And:

#include <errno.h>
#include <stdio.h>

int main (void) {
    errno=ENOANO;
    perror("");
    return 0;
}

Yields:

$ ./a.out 
No anode
$

Note that on current, systemd-based systems, one probably wants sudo journalctl -kb to show kernel messages for the current boot.

dmesg reads from the in-memory kernel ring buffer. That can be desirable in some cases, but as the name suggests, the “ring buffer” is a “ring” — it has a finite amount of space and eventually, the old stuff gets overwritten by the new stuff. The idea is that a userspace logging daemon, like journald (or syslogd on most older systems) has time to pull the data from the ring buffer out to (potentially much larger) log files on disk.

journalctl will also post-process the output to do things like convert the time-from-boot to a wall clock time, which is generally more useful for correlating with other things.

I think that the point being made here is that it’s not a great idea to hold an actually running soldering iron by the hot bit?

If so, I think that OP’s image is supposed to have some sort of thermal insulation stuff around the hot bit, that clear stuff.

If you don’t want it, you can hide it — most distros have some way to just show a splash screen that hides it. I always unhide it, as I can see hints of things going wrong.

The messages are from a wide variety of kernel subsystems (and, later in the boot process, daemons) and most people aren’t going to be familiar with everything. I could tell you what a lot of lines mean, but there are always new ones showing up as new software is written.

They’re more-likely to be useful if something breaks and then you go examine a specific, suspicious-looking message and learn what it means. You probably won’t be constantly trying to stay up on all kernel subsystems.

When I looked at condensers in the past, they weren’t incredibly energy-efficient. I suspect that it’s cheaper in the long run to do desalination and build a pipeline to wherever inland you want freshwater, unless you have very limited-in-scale need.

Nah. He just has a very high willingness to lie or misrepresent anything. Like, no regard for reputation or consistency or anything. He’ll make entirely-contradictory statements depending upon occasion. If he thinks that it will buy the slightest iota of political oomph to say that Anthropic is violating the Constitution, he’ll do so, even if he doesn’t have the slightest grounds to make that statement.

It doesn’t matter if you’re, say, Debian, because they’ll just put up some symbolic “not intended for use in state X” and then continue doing whatever they were doing, but if you’re Red Hat and actually selling something like Red Hat Enterprise Linux to companies in the state, stuff like this is actually a pain in the ass.

And to reiterate a previous comment, the Democrats have a trifecta in both California and Colorado, and the legislation here is something that they are squarely to blame for. I’d really rather that they knock this kind of horseshit off so that I can go back to being upset with the Republican Party.

The Democrats have a trifecta in both Colorado and California. I really wish that they’d knock bullshit like this off so that I could go back to being upset about Trump and company.

If it happens again and you have Magic Sysrq enabled, you can do Magic Sysrq-t, which may give you some idea of what the system is doing, since you’ll get stack traces. As long as the kernel can talk to the keyboard, it should be able to get that.

https://en.wikipedia.org/wiki/Magic_sysrq

You maybe can’t see anything on your monitor, but if the system is working enough to generate the stack traces and log them to the syslog on disk (like, your kernel filesystem and disk systems are still functional), you’ll be able to view them on reboot.

If it can’t even do that, you might be able to set up a serial console and then, using another system running screen or minicom or something like that linked up to the serial port, issue Magic Sysrq to that and view it on that machine.

Some systems have hardware watchdogs, where if a process can’t constantly ping the thing, the system will reboot. That doesn’t solve your problem, but it may mitigate it if you just want it to reboot if things wedge up. The watchdog package in Debian has some software to make use of this.

I’m not sure that memory — and I’m speaking more-broadly than HBM, even — optimized for running neural nets on parallel compute hardware and memory optimized for conventional CPUs overlap all that much. I think that, setting aside the HBM question, that if we long-term wind up with dedicated parallel compute hardware running neural nets, that we may very well wind up with different sorts of memory optimized for different things.

So, if you’re running neural nets, you have extremely predictable access patterns. Software could tell you what its next 10 GB of accesses to the neural net are going to be. That means that latency is basically a total non-factor for neural net memory, because the software can request it in huge batches and do other things in the meantime.

That’s not the case for a lot of the memory used for, say, playing video games. Part of the reason, aside from hardware vendors using price discrimination that PCs (as opposed to servers) don’t use registered memory (which makes it easier to handle more memory) is because it increases latency a little bit, which is bad when you’re running software where you don’t know what memory you’re going to need next and have a critical path that relies on that memory.

On the other hand, parallel compute hardware doing neural nets are extremely sensitive to bandwidth. They want as much as they can possibly get, and that’s where the bottleneck is today for them. Back on your home computer, a lot of software is oriented around doing operations in serial, and that’s more prone to not saturate the memory bus.

I’d bet that neural net parallel compute hardware does way more reading than writing of memory, because edge weights don’t change at runtime (on current models! That could change!).

searches

Yeah.

https://arxiv.org/html/2501.09605v1

AI clusters today are one of the major uses of High Bandwidth Memory (HBM). However, HBM is suboptimal for AI workloads for several reasons. Analysis shows HBM is overprovisioned on write performance, but underprovisioned on density and read bandwidth, and also has significant energy per bit overheads. It is also expensive, with lower yield than DRAM due to manufacturing complexity.

But there are probably a lot of workloads where your CPU wants to do a ton of writes.

I’d bet that cache coherency isn’t a huge issue for neural net parallel compute hardware, because it’s going to be a while until any value computed by one part of the hardware is needed again, until we reach the point where we can parallel-compute an entire layer at one go (which…I suppose we could theoretically do. Someone just posted something that I commented on about someone making an ASIC with Llama edge weights hard-coded into the silicon, which probably is a step in that direction). But with CPUs, a big problem is making sure that a value written by one CPU core reaches another CPU core, that the second doesn’t use a stale value. That’s gonna impact the kind of memory controller design that’s optimal.

I think that it’s fair to say that AI is not the only application for that hardware, but I also think that carpelbridgesyndrome’s point was that they aren’t really well-suited to replace conventional servers, where all local computing just moves to a server, which is the sort of thing that ouRKaoS was worried about. Maybe for some very specialized use cases, like cloud gaming in some genres. I’d also add that the physical buildings have way more cooling capacity than is necessary for conventional servers, so they probably wouldn’t be the most-cost-effective approach even if you replaced the computing hardware in the buildings.

Once all of those who objected to the government and presented possible opposition have been eliminated one way or another, society will be harmonious.

Well, not all forms. The State of New York runs a lottery itself, for example:

https://en.wikipedia.org/wiki/New_York_Lottery

On November 8, 1966, New Yorkers voted to approve a constitutional amendment authorizing a government-run lottery.

checks

The 5700X3D looks like it goes for about $350 on eBay. The 5800X3D looks like about $450.

I sat down to log into a couple MUDs yesterday. Didn’t stick with it — the combat still hasn’t evolved enough for me — but you could play that on anything capable of displaying text on a screen and running telnet.

It looks like some crazy person has been doing a TCP/IP stack for the 128K Mac, the first Macintosh ever released, from 1984, as well as a telnet client. So you can technically lug a 42-year-old computer out of an antique store and play currently-being-developed Internet games…though you won’t be getting color, since that came a while down the road.

If you get some device that can expose a serial console on some system to TCP/IP — not sure how far back you need to go for that — you could technically play it on a teletype from the 1930s.

The “some device” will have to be later, though, so that’s maybe kinda cheaty.

Technically, Debian Linux has been run on an Intel CPU from 1971, but it isn’t fast enough to be a practical host for such a teletype in that environment. Even stripped down forms of Linux are going to be “too big” to be such a host.

It does sound like the Commodore 64 has a package, Novaterm 10, that runs TCP/IP and telnet, but I don’t know whether it can output to the C64’s serial port rather than video display; you could play locally on one of those, but probably not run on a teletype. That being said, it probably shows that it’s technically-possible, since I’m sure that if it can run a virtual terminal program, it has the resources to just dump the text to an actual terminal via a serial port. I’d guess that there’s probably some system out there circa 1980 that someone has probably built that can both run a TCP/IP stack and expose a serial console to a 1930s teletype to play current Internet games.

I agree with you that it’s a good game, and it’s very playable on an older computer, but it’s actually not the lightest-weight game from a CPU standpoint. I mean, realistically, that thing should be able to get by with very little CPU usage and essentially none if you’re not pushing buttons, but it actually uses a fair bit of CPU time when you’re just sitting there staring at the screen. It’s actually kind of bugged me, because while it’s irrelevant on a desktop, it really consumes more battery on a not-plugged-in-to-wall-power laptop than is necessary, and it’d otherwise be such a phenomenal game for disconnected laptop use.

Go run top and just leave the game sitting there and it’ll be keeping an average of multiple cores hot on my laptop at 240 Hz running at vsync rate. And the world state isn’t changing – the game is turn-based.

You can constrain the framerate down to 10 FPS — and that significantly reduces CPU usage, down to an average of 37% of a core, on my system, at the cost of limiting the speed at which the game runs autoexplore, since it will always draw at least one frame in a given state, and at the cost of making the game feel sluggish and unresponsive.

And you’ll get that CPU usage even if you turn off all the graphical “glitz” have it just showing ASCII.

My guess is that they probably could probably benefit by (a) having a lightweight visual “display” thread that doesn’t do anything expensive, just update any animations and draw that to the screen, and if there are no animations, not even run a refresh at all, and (b) having a separate “heavyweight” thread for game logic that only runs if the world state has changed (autoexplore, automove, resting, or the player has pressed a key).

Cataclysm: Dark Days Ahead, which is a similar game (internally a turn-based game that’s basically generating an ASCII grid that can provide some light graphical glitz and tiles) also consumes a lot of CPU time when idle.

If you want another game of a similar sort that uses a surprising amount of CPU time, Dwarf Fortress. That being said, Dwarf Fortress is real time, so one can’t beat it up as much for consuming CPU time while the player is idle.

It’s still running. I submitted an article last month about how Micron was buying a facility that had actually just opened quite recently and was apparently producing DDR4 to refit it to make HBM; faster than building a new memory factory from scratch.

But as I point out in another comment in this thread, my guess is that this is more about being able to tap the already-manufactured used memory market. There’s a lot of DDR4 already in computers, and as those computers get disposed of, as long as it’s not thrown out and goes back on the market, that makes DDR4 available.

My guess — without trying to dig up statistics — is that the single component most-likely to fail in an old PC is gonna be rotational hard drives. Virtually all of my rotational drives have eventually died, aside from a few that were just so small and taking up space where I could mount other things that I no longer bothered using them.

I’ve seen fans die (not necessarily completely wedge up, but have the bearings go and become increasingly-obnoxious in sound).

And those are basically the only mechanical components in a computer.

Behind that, there’s input devices with keyswitches wearing out, but unless you’re using a laptop, replacing the input device is just unplugging the old one and plugging in a new one.

I’m not gonna say that motherboards don’t fail, but I can’t immediately think of something that would die. Decades back, I remember that there was a spate of bad capacitors that made their way to a bunch of motherboards and would eventually fail, but I haven’t seen anything like that recently.

searches

Looks like it was 1999–2007:

https://en.wikipedia.org/wiki/Capacitor_plague

The capacitor plague was a problem related to a higher-than-expected failure rate of non-solid aluminium electrolytic capacitors between 1999 and 2007, especially those from some Taiwanese manufacturers,[1][2] due to faulty electrolyte composition that caused corrosion accompanied by gas generation; this often resulted in rupturing of the case of the capacitor from the build-up of pressure.

High failure rates occurred in many well-known brands of electronics, and were particularly evident in motherboards, video cards, and power supplies of personal computers.

A 2003 article in The Independent claimed that the cause of the faulty capacitors was due to a mis-copied formula. In 2001, a scientist working in the Rubycon Corporation in Japan stole a mis-copied formula for capacitors’ electrolytes. He then took the faulty formula to the Luminous Town Electric company in China, where he had previously been employed. In the same year, the scientist’s staff left China, stealing again the mis-copied formula and moving to Taiwan, where they created their own company, producing capacitors and propagating even more of this faulty formula of capacitor electrolytes.[3]

Those would probably be from the DDR/DDR2 era, though.

I do think that it’s probably possible that some motherboard components might age out. Like, people may want to use newer versions of radio stuff, like WiFi or Bluetooth. You can maybe do that via USB, but the on-motherboard stuff might become more of a liability than the CPU or something.

I don’t think that I’ve ever personally had other computer components just up and fail other than the 13th and 14th gen Intel CPUs that internally destroyed themselves. It’s always been non-solid-state stuff, things with moving parts, that fail for me. I mean, I’ve damaged solid-state components myself via things that I’ve done, but it’s always damage that I incurred.

thinks

Oh, CMOS batteries eventually fail, but they’re usually — not always — mounted on motherboards with holders that permit replacement. I’ve had to replace those.

I did have a headphones amplifier that was attached to my computer where some solder joints got a bad connection and I had to open it and resolder it, but I don’t know if I’d call that a “computer component” just because it was plugged into a computer.

thinks more

I did have the power supply used for a fluorescent backlight in a laptop display start to fail once. But, honestly, my experience has been that unless you actively go in and damage something, most solid state parts will just keep on trucking.