Many G-code dialects contain subprogram calls, loops, and conditionals that seem like they'd permit a physical quine. The standard RepRap firmware breaks the rules by taking input:

https://reprap.org/wiki/G-code#M98:_Call_Macro.2FSubprogram

but Fanuc and other dialects allow M97 to call a subroutine chained to the end of a program.

This is how you get statutory warning labels and nutrtion information labels on packages.

Because these folks always want to do the least legal thing allowed by law.

> The switches start out gray and become black when toggled.

Rant: That type of slider-switch is an inferior usurper of the classic tickbox, that rode in on a wave of touch-screen-ification. Oh, it can be done well, sometimes, but it's just far-too-easy to do it badly.

In this case (useless colors, no other labels, etc.) I think the remaining rule/clue is "Move the dot-nub towards whatever you want." So moving right is indicating you like the "We track you" text, while moving left indicates some kind of disagreement.

_____________________

> It feels intentionally misleading.

The "Accept All" button is worse:

1. It abuses UI conventions of position and color so that it appears like a "Proceed with the configuration shown" button.

2. This is worsened by the label-text ambiguity. It could mean "Accept All [of the choices which I've made and can see]", which the user has been set up to expect... But it doesn't, it means "Reject what is shown, set every discrete option to accept tracking."

3. When it does reset all those your choices, it does so in a secretive way by also dismissing the dialog. The user never has any opportunity to see that it just flipped every item to the rightmost position.

Any one might be an innocent mistake, but all three sins is a dark-pattern.

Don't print the braille document directly. Instead, I suggest printing a braille embosser. Think Gutenberg press. Then use that to press braille lettering onto a sheet of paper.

Although if you just want one sheet, I guess you could use the print directly, but maybe don't use PLA since it'd be kinda sharp and unpleasant to run your finger over.

I've also been idly contemplating 3D printing braille. Somewhat annoying that that's the cheap+easy option, but if it works...

:)

There's probably a way to make an xz file that decompresses to g-code for itself. But plain g-code is not powerful enough because it's just a list of movements due the tool head to perform - no computation.

It's fascinating how revered people are who talk in metaphor and implication like this about relatively simple things, when far more complicated things are happening all the time inside their devices.

G-code by itself only describes the series of motor movements over time, though I think it would be practically feasible to have a book contain an executable script, which would generate the same g-code as the one used to print the book. It would be really interesting to see how large the resulting book is.

"This prompt, when fed to a sufficiently capable LLM, will generate the G-code to produce a 3D printed model of a book containing this quote, verbatim, in raised letters."

Compression could be interesting