Revisting with note to self: modified bash version of hidden executed payload ("ls -al") with only 51 visible bytes:
echo -n 󠅬󠅳󠄠󠄭󠅡󠅬|iconv -tUCS4|tr -d \\000-\\016|xargs xargs
Even shorter, but a bit OBVIOUS:
$(echo -n 󠅬󠅳󠄠󠄭󠅡󠅬|iconv -tUCS4|tr -d \\000-\\016)
Or, even better:
U+FFA0 HALFWIDTH HANGUL FILLER
U+FE09 VARIATION SELECTOR-10
Since the first 6 UCS-2 bytes are trimmed, FF A0 FE 09 becomes %09. A tab.
FFA0 valid ID_Start; FE09 (as all variation selectors) valid ID_Continue.
Whole payload as invisible identifier.
I just discovered that macOS 14.x adds an invisible character to its screenshot filenames just before the AM/PM that breaks compatibility with older image editors and other software
Unicode 8239: "Narrow No-Break Space" (U+202F)
Anybody know a member of the macOS dev team?
@lorenschmidt@frozenpandaman@FakeUnicode I did some research about how browsers obey variation selectors and forced fonts and summarised them around here: (tl;dr: yes, inconsistent even for glyphs that are told to be "monochromatizable" by Unicode standard.)
https://t.co/7xwyOiYm9e
pet peeve: as technological detritus from the era when every corporation was trying to cash in on the popularity of emoji, many unicode characters now are automatically replaced with emoji variants. even in text editors.
@anaxium You can look at old versions on unicode.org, eg:
https://t.co/GIm3pggXhb
https://t.co/WLR625o705
https://t.co/64S2Nlazbl
But really, Unicode never renames, removes, or moves anything: https://t.co/FV3aDqvdc3
(Only non-fundamental changes are allowed, like updated glyphs, etc)
@xah_lee @SUPER7X_ @sigfig What is more confusing is why there are two of them
⋚ U+22DA 8922 LESS-THAN EQUAL TO OR GREATER-THAN
⋛ U+22DB 8923 GREATER-THAN EQUAL TO OR LESS-THAN
tldr: math is nuts
https://t.co/brrpWZjUw7