Mon mon-jai

Note

Hi, everyone. I've been putting in a lot of work on this over the last few ~~weeks~~ months (sob) and i'm currently underemployed! If you'd like to hire me to do CMS-based work (i focus on Craft and ExpressionEngine but i do some WordPress work as well), please reach out! Alternatively, if you'd like to chip in toward bills & groceries, that's a big help right now!

Updates (Most Recent First)

13 February 2025
8 February 2025
7 February 2025
6 February 2025
23 January 2025

FAQ on the xz-utils backdoor (CVE-2024-3094)

This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.

Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.

Background

Dogfooding

Dogfooding is using an app or feature shortly before it's publically released.
The term dogfood comes from the expression "eating your own dogfood".

Fishfooding

Fishfooding is using an app or feature really early in its development before it's even really finished.
The term "fishfood" actually comes from the Google+ team inside of Google.
Google+ was internally codenamed Emerald Sea.

Unity versions not affected by Unity Runtime Fee

This is information that has been dug up by me and others in the Unity community. It's not official information from Unity (but most of the linked resources are). It is also not legal advise. I am not a lawyer.

TLDR:

Contrary to what Unity themselves are saying, for games made with these Unity versions, developers can elect not to be affected by a newer version of the Terms of Service that introduces the Unity Runtime Fee:

Unity 2022.x or earlier
Unity 2021.x LTS or earlier

Node con TypeScript - TS-Node-dev (preferido)

Instalar TypeScript y demás dependencias

npm i -D typescript @types/node ts-node-dev rimraf

Inicializar el archivo de configuración de TypeScript ( Se puede configurar al gusto)

npx tsc --init --outDir dist/ --rootDir src

The ffast and the Furious

This is a small and admittedly contrived demo showing how some weird but safe code could become vulnerable if run in an environment where some shared library has changed the FPU's FTZ/DAZ bits to force denormals to zero.

To run it:

# Create an empty file
$ touch gofast.c

brew is a bad neighbor

This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.

This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".

But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.

By following this guide you will:

Never have to run sudo to forcefully change permissions of some directory to be owned by your account

In the last years I've been asked multiple times about the comparison between raylib and SDL libraries. Unfortunately, my experience with SDL was quite limited so I couldn't provide a good comparison. In the last two years I've learned about SDL and used it to teach at University so I feel that now I can provide a good comparison between both.

Hope it helps future users to better understand this two libraries internals and functionality.

	$ grep -P "^[ABCDEFabcdefOoIi]{6,6}$" /usr/share/dict/words \| tr 'OoIi' '0011' \| tr '[:lower:]' '[:upper:]' \| awk '{print "#" $0}'
	#ACAD1A
	#B0BB1E
	#DEBB1E
	#AB1DED
	#ACAC1A
	#ACCEDE
	#AC1D1C
	#BAB1ED
	#BA0BAB