balou23

No, it's by changing the refractive index of the water in the chicken.

If you scroll down a lot, the post goes into details.

I have to admit, it's a bit hard to follow the exact details as a non-physicist on a lazy sunday morning... but you change the refractive index by uhh... something related to the polarization and Maxwell's equations

LAHF and SAHF are an interesting rabbit hole themselves.

If you ever dug into x86 assembler programming... at first they make no sense at all. They only save/restore a tiny part of the available flag registers. The mnemonics themselves make little sense - load/store are not really used in any other base x86 mnemonics (unlike e.g. 6502 mnemonics, which use LD?/ST? instead of MOV like x86).

It only clicked when I read an Intel document about porting assembler code from the 8080 to the 8086.

LAHF/SAHF are basically convenience instructions to make porting easier. Many 8080 instructions did not alter the flags, unlike their 8086 counterparts. Substituting an `INX` instruction with `LAHF; INC; SAHF` made it possible to mechanically translate assembler source code.

And yeah, 8080 mnemonics had LDA and STA like the 6502...

amazon.de, spiegel.de are down for me, too. heise.de works, but that might've been cached somewhere on my side.

It seems to have similar ideas, but two big differences seem to be that 1. it's based on git 2. more focus on a truly decentralized p2p architecture

Hats off to you for just saying "no" to optimizations.

I'd have gone down an optimization rabbit hole, while never finishing the original project.

TBH I still don't really get how it's different from MIPS. As far as I can tell... Loongson seems to be really just MIPS, while LoongArch is MIPS with some extra instructions.

At some point there were LCD monitors that had very noticeable to me chequerboard pattern - like with analogue TV, only half of the screen got lit up/refreshed, but with an alternating pattern rather than scan lines.

After asking the owner of said screen how he could stand that... "stand what?"

Yep, I guess most people are not that picky.

You'd better be, we have certain expectations from you now /s

But more seriously... I don't think that Linux has ever been booted on a non-monolithic CPU (I wanted to say 'discrete cpu' first, but there's some PDP-11s with 4 chip CPUs)

I'm by no means an expert, but I've recently implemented a small BLE based IoT device, and had a look at the security/privacy of a medical BLE device.

Some points:

* there's a real lack of quality, up-to-date documentation. I would have thought that at least on Linux you'd find some documentation, but most of it seems to be "RTFS".

* BLE is in general very unfamiliar to most developers. There's no client and server, there's central and peripheral. GATT profiles are a mix between TCP connections and binary REST-ish interface.

* Encryption/authentication is possible, but depending on the manufacturer's API/quality of documentation it's not really apparent a. how to select a secure connection method b. how to even check if and which authentication/encryption was chosen

* Coming from the previous point, many BLE devices have the same generic GATT profiles, sometimes with the same sample data. This looks like a lot of BLE devices just copy&pasted sample code from the manufacturer and added the minimal changes "to make it work"

* It's probably really easy to do passive/active fingerprinting to find out the manufacturer and/or chip version used in a device. Default services, ordering of advertising options etc

* Many BLE devices are not conformant. Uninitialised name fields with garbage in them ("Device Name: WHOOP\020��=u5״\023n"), manufacturers using random identifiers that clearly don't belong to them

* when doing passive BLE sniffing: the biggest obstacle isn't getting data. It's how to filter it. One of the most useful filters of the nRF Connect app for android is to filter out all advertisement packages for apple and ms devices, to cut down the overwhelming amount of such devices

I hear you.

Coincidentally, if anyone knows how to figure out which Intel CPUs actually support 5-level paging / the CPUID flag known as la57, please tell me.

Ah memories...

Nmap used to have a mode where you could portscan via a third-party FTP server.

And it just so happened that HP Laserjet printers had an FTP server active by default that allowed PORT to any IP.

Very low bandwidth situations, or when you want to apply the same steps to other files afterwards.

But if you're totally comfortable with vim you'd better use ex, which basically is both an extension to ed, and the non-interactive part of vim.

There's plenty of options available. A coworker of mine used to print out code for reviews. You can use italic, bold and underline as alternative to colors. Grayscale might work nicely for eInk too - for laser printers just thin/regular/bold probably works better.

Other fonts... I could see myself being distracted by changing fonts in a document, except maybe for comment blocks. But for those italic/thin seems to work well already.

Tried to find the tool... it's GNU enscript. Syntax highlighting for several languages, outputs to postscript.