Re:The cats sitting on a fence in early builds of Windows 8
by mjg59 on Wednesday February 23, 2022 @03:59AM
(#30439159)
Although the fact that I've since encoded the "UUID" that this is contained within into other codebases such that Linux can't remove it without breaking some deployed u-boot builds is definitely something I'm proud of.
Re:The cats sitting on a fence in early builds of Windows 8
by Jaruzel on Wednesday February 23, 2022 @04:12AM
(#30439224)
Your mention of UUID, reminded me that the GUIDs for Microsoft office products in the Windows Registry all end with '0FF1CE' - that's a nice Easter egg I think that doesn't impact anything.
Re:The cats sitting on a fence in early builds of Windows 8
by dspillett on Wednesday February 23, 2022 @06:04AM
(#30439871)
I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data. And for a while one was floating about in production where it would appear in URLs for anyone who cared to look to see¹, because someone else took a bit of my PoC work and shoved it where it didn't yet belong without review…
[1] not just in the middle of a sea of otherwise arbitrary hex either, something like 00000000-0000-ABAD-IDEA-000000000000 so it was easily visible as a “test” value.
Re:The cats sitting on a fence in early builds of Windows 8
by reaperducer on Wednesday February 23, 2022 @12:07PM
(#30443361)
I use ABAD1DEA somewhere in UUIDs in experiments/examples & proof of concept code/data.
DEADBEEF shows up regularly if you work on projects that have only a seven-segment display.
Re:The cats sitting on a fence in early builds of Windows 8
by stavros on Wednesday February 23, 2022 @04:19AM
(#30439257)
But those bytes could randomly be in anything, doesn't mean they're interpreted as Unicode, no?
$ grep -o --text U+1F4A9 vmlinux
U+1F4A9
and while there may be an argument that this is whimsical, I don't think there's an argument that it's beautiful.
(U+1F4A9 should be the literal Unicode PILE OF POO glyph, but HN strips it, so)