JATth

You can’t exceed lightspeed. Current tech is already at 99%

Even the newest “64-bit” cpus are really just 48-bit (or 36-bit on low end) or if bleeding edge 56-bit physical adressing processors. This is the maximum amount of virtual memory a process can have access to. You could memory map all your hard disks an still have room to map more physical memory to VMA.

I once said that the current “AI” is just a excel spread sheet with a few billion rows, from what all of the answer gets interpolated from…

But it’s the spaghetti cabling that makes it work and highly robust.

So, now they are slowly (or immediately and forever, I don’t know the time span) injecting propaganda into their clone of wikipedia and they are simultaneously thus admitting they are doing it. (to further brainwash the russian citizens)

So lettme repeat: FUCK PUTIN, and stuff your rubber clones in your ass. (which there are many of)

The in-rush of endorphins when the modded LCD thing actually worked probably knocked you out?

A bit of a side story: I disassemble probably 1–5 panels in a week. (For recycling, it takes about 20-45min per panel.) The flat cables alone are so flimsy, I would say just assembling a display again from known, matched and functional parts would take days. I would triple or quadruple that to assemble a display from random parts. Considering this, that modded panel is quite amazing to me.

In standalone panels, the PSU has a chance of killing you: the main capacitors can hold multiple joules worth of nope, charged to about 400v. So, if the main caps are not allowed to discharge (if they discharge at all that is), there is a possibility of death when disassembling a panel with an integrated PSU. Waiting “5min” is bad; a PSU needs to be unplugged for a day or two at least before the charge drains out.

I would highly recommend Curve25519, etc., just because such keys are faster and less common than RSA public-private keys in today’s world. RSA 2048-bit keys are considered weak today, while the Curve25519 256-bit keys remain stronger. Also, the ChaCha20-Poly1305 cipher has an interesting backstory and doesn’t necessarily need hardware acceleration (which, in theory, could be borked by the HW-vendor) to obtain good performance.

Unfortunately, some SSH front-ends don’t play nice with Curve25519 public-private keys yet… (I’m pointing at the putty SSH client, but that may have improved from the last time I had to use it)

The backdoor has existed for a month at least. Yikes.

https://www.openwall.com/lists/oss-security/2024/03/29/4

Gamma rays have so much energy that they are basically emitted only by nuclear processes, as far as I know.

Maybe not in a flashlight, but the scientific industry would be very pleased with them. Sterilize water and all surfaces in a second? Flash with 200nm light.

This was an yet another glorious episode from veritasium.

I hope we get well past UVC LEDs. (i.e., shorter wavelengths) UV LEDs are already available. Unfortunately, this progress will stop before X-ray light. With +1 KeV energy, you pretty much must blast off the electrons from the atoms to emit X-rays, which an x-ray tube already does. Or by peeling off a piece of scotch tape.

I read the article enough to find that the Nightshade tool is under EULA… :(

Because it definitely is not FOSS, use it with caution, preferably on a system not connected to internet.

Windows: $ insmod < “http://shady-ring0-blob-from-internet.sys.cn” What could possibly go wrong?

Shorter version: Operating systems set up hardware locks and protections to confine processes, and once set up, they cannot be undone. (the hardware + OS denies modifications to the security policy)

• Attacker broke out from the app sandbox. (attacker can run code in the infected process)
• Broke out of the process. (gained root access; attacker can run anything)
• Broke into the kernel space (gained 100% control over the hardware)
• Corrupted some kernel memory via a damm magic MMIO accesses nobody knows (hardware vulnerable)
• Bypassed protections that kernel set up earlier such that it cannot accidentally modify itself.
• Finally broke the kernel via hardware exploit thus the attacker got rootkit level access.

Getting arbitrary code execution and root access is one thing, but breaking out from the damm kernel configured hardware protections is insane.

They basically managed to flip a “read-only” switch to “modify-as-much-as-you-like”. The infected device at this point is broken beyond repair, as the firmware(s) may have been tampered with. End result is a terrestrial spy brick.