https://www.cnet.com/news/how-eight-pixels-cost-microsoft-mi...
https://devblogs.microsoft.com/oldnewthing/20030822-00/?p=42...
https://www.cnet.com/news/how-eight-pixels-cost-microsoft-mi...
https://devblogs.microsoft.com/oldnewthing/20030822-00/?p=42...
Instead, there are https://en.wikipedia.org/wiki/Regional_Indicator_Symbol — an symbol-alphabet where any pair of successive symbols from the alphabet are meant to be considered a ligature (so, a space of 36^2 = 1296 possible ligatures), where a subset of these ligatures are considered valid representations of a locale from the Unicode's https://en.wikipedia.org/wiki/Common_Locale_Data_Repository.
Unicode doesn't say that you should render these CLDR-valid locale meta-codepoints as flags, though. It just says they're locales. In other words, it's up to a given font to decide whether to draw these as flags, and which of them to draw as flags.
With this move, they've abdicated the political determination over to, mostly, the OS manufacturers (since right now most OSes just have one OS emoji font that gets used for the graphical-pictograph-rendering process, rather than allowing user-installed emoji font-families.)
Personally, I like this choice. No matter what any government says, Taiwan is its own locale—it has its own time zone, clock and currency display formats, etc. Locales are locales no matter who declares ownership over them. Having "locale icons" rather than geopolitical-region flags is probably the most stable arrangement we can have, even if it means that some OSes will just render a particular locale-icon as nothing.