The explanation which makes most sense to me - but which hasn’t been confirmed by GOG - is that the newsletter person did a web search for “slavic emojis”, for which the top hit is a horribly racist website masquerading as an emoji site, which lists all the used glyphs on the first line of the results. (There is no “Slavic” unicode block or anything similar, and the characters used are from Malaysian, Greek and Cameroon script blocks, so not something you’d easily assemble on your own, no matter what your intentions were.)

That site (or at least the users contributing its content) intended all the dog-whistling which was picked up on. However, with a default macOS font installed, the most objectionable “SS” (presented on that site as a single glyph) shows all curly and non-objectionable (5th ‘character’ in the screenshot). So with the newsletter person in a hurry and never scrolling down to the more obviously racist content (or using an AI-assisted interface?), the characters they saw didn’t trigger any alarms. As GOG is perpetually understaffed plus it was a long-weekend, QA was nearly non-existent and communication fumbled.

This was their final apology and communication about it: https://www.gog.com/upload/forum/2026/06/c1cdf9fda39aaa5532ee375b38abb04376c7505d.png - so an apology about the newsletter, but nothing about the tone-deaf first followup from the new-on-the-job “community specialist” who was posting the heritage stuff on reddit and ineffectually trying to make sense of the rendering differences without any proper understanding of unicode characters and glyphs and thus muddying the waters further.