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 wish lemmy communties existed for:

• 1. How are you doing today?
• 2. Did you discover anything new to your consciousnesses today?
• 3. I fucke’ed today. Here is how.

Edit: yeah, I think I miss a few of the old subreddit’s. Even if there is an equivalent in lemmy, such communities are quite silent.

You want benzodiazepines? They are basically erase memory from [0.00 to 24.0] so I definitely wouldn’t recommend.

Cryptographic CSPRNG seed? No way I’m telling that.

BTW. With clang lto’d kernel 6.9. When non-Arch get the buggy updates, We have already moved on.

Wayland has much more up-to-date graphics technologies behind it to put it simply.

Mint was the distro that converted me. After 8-10 years, I’m still using the cinnamon DE, but just on top of Arch. Next hope is the devs port it over wayland so I can also ditch xorg. (There is a demo/alpha available)

What’s happening in the area, I.e. a view of the overall scenery. This vast perspective is different, and it’s like looking at a live painting. When I’m on the move, such a observer perspective shrinks to few tens of meters, which kind of makes sense.

I don’t think this is anything most people don’t do however. I do remember places quite vividly though, and I practically never get lost. People however in the scenery, I forget in about a minute.

I try to filter out most of this negative stuff, but it has a downside. You become disconnected from the raw information feed if you don’t occasionally just look at it. For short periods, it’s tolerable, but then I just re-enable all filtering to reduce my cognitive load.

If I need to be cheered up, I prefer to look for science articles or news since these are generally about unbiased progress.

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 put too way too much effort in this reply… Yes… it’s nerve racking, especially if you are resorting to BIOS flashback to boot the CPU on an older (new) board.

Can’t get visuals (except maybe leds/indicators on the motherboard itself) when your CPU is incapable of accessing the ram or the devices yet. All external devices normally communicate through the RAM. (And by external, I mean not on the CPU package) Yet, the CPU has to solve out this chicken-and-egg problem of how to progress from the cold-boot without knowing what external RAM is installed. There are plethora of timing/clock-cycle/voltage settings for one stick of ram, which are tested on POST. Establishing sane DDR5/4 parameters is non-trivial. (I think it is order of +20!, twenty factorial: 2432902008176640000, if there were no starting point of XMP, JEDEC etc.)

I use hand tuned settings for DDR4, and on cold boot, the BIOS adjust the settings which I didn’t forbid it to do. Unless I unplug the PSU from the wall, the BIOS won’t retrain the memory again. I suspect my settings still aren’t 100% stable. (over period of years) Non-cold-boot assumes the ram works 100% same on each power up. If some OC setting drifts past a threshold once the system is heat soaked or receives more EMI interference, this could provoke a crash/BSOD etc. in absurd theory having a busy wifi router next the ram could cause the bios to select more robust/conservative settings to counter the EMI interference. Would be fun to know, if this would be true.

I just did: “rm -rf xz”

pacman -Syu
find / -name "*xz*"  | sort | grep -e '\.xz$' | xargs -o -n1 rm -i 
pacman -Qqn | pacman -S -

(and please, absolutely don’t run above as root. Just don’t.) I carefully answered to retain any root owned files and my backups, despite knowing the backdoor wasn’t included in the culprit package. This system has now “un-trusted” status, meaning I’ll clean re-install the OS, once the full analysis of the backdoor payload is available.

Edit: I also booted the “untrusted” system without physical access to the web, no gui, and installed the fixed package transferred to it locally. (that system is also going to be dd if=/dev/zero'd)

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

The first kernel I built was not entirely happy with the .config I had made for it. Only thing it could do was BEEP-ing in panic for any key presses. [insert noot noot meme]

BIOS/UEFI likely tried to fuck up the CPU, or hardware fault. NMI => Non Maskable Interrupt.