I got a REAL ID several months ago and definitely didn't get fingerprinted in the process.

williamvds's point is that the first argument to printf is still itself a null-terminated string, so it's basically turtles all the way down if you're using the C standard library.

Their comment talked about two things, and the sibling comment addressed the other one.

Not quite, at least not necessarily. One feature of FTDI chips is an EEPROM that can be used to customize the enabled features, enumeration strings, and other things. That programming could probably be done in a separate jig, or in-circuit. So yes, 5 minutes of hardware work, but more potential rework at a higher level.

Not to mention the possibility of sealed cases/enclosures or potted PCBs.

> The community has migrated over to Spacemacs

I'm guessing you meant to say Doom Emacs there?

I did! Thank you for the correction. Editted.

Not in core Python, but in a widely-used library, yes. https://github.com/pyca/cryptography/issues/5771

We actually got a picture like 3 minutes after landing. (Okay, a picture from shortly after landing.)

Probably routed through the Mars Reconnaissance Orbiter, Maven and possibly Europe's Mars Express satellites, rather than a direct connection to the Deep Space Network

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

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

If I understood the livestream correctly, it's because they were able to (maintain|quickly establish) lock to the MRO after touch-down and zip a couple of images up through the "bent-pipe" UHF-to-high-power relay into the Deep Space Network.

It would seem they had MRO in position to snap a few photos of the landing / descent as well as do the relay.

By resizing my window down to mobile-ish width, the "get your free e-book" thing on the right side covers the whole screen.

Not to mention some IOT devices or cellular routers/devices might force a longer minimum cache TTL, to "minimize data usage". I worked on a device that did so (minimum pdnsd cache time of 25 hours). It ended up causing failures when our cloud server did a cut-over, dropping the TTLs 24 hours in advance. :(

But, that link shows mmap taking 6 arguments?

The parent comment talked about the syscall, not the library function.

   return((caddr_t)(long)__syscall((quad_t)SYS_mmap, addr, len, prot,
       flags, fd, 0, offset));

The first argument is the syscall number, the rest are the seven arguments in question.

They're implemented using metaclasses. Metaprogramming is a part of the language.

I know that, there's a lot of magic going on due to that choice of indirect implementation.