this post was submitted on 15 Jul 2026
1491 points (99.2% liked)

PC Gaming

15053 readers
342 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Syrc@lemmy.world 6 points 1 day ago (1 children)

Is this about the Gog Newsletter thing? I’m not 100% informed, but didn’t they pretty much admit that they weren’t aware that ᛋ displayed as ϟ in some devices?

It’s not even a “sorry we got caught” thing, they had nothing to gain by sending a Nazi symbol in their newsletter. What more are they supposed to say?

[–] Jako302@feddit.org 1 points 1 day ago (1 children)

They specifically didn't send it to German accounts cause they knew it could be shown as Nazi symbolism.

This isn't a "sorry we fucked up" this is a "we knew it could go wrong but didn't care enough to do anything about it".

Personally I don't really care that much. These promotional emails aren't reviewed by every company member, so even if it was deliberately used Nazi symbolism, its at most someone in the advertising department. But I also understand why people are really upset about this.

[–] Doc_Crankenstein@slrpnk.net 4 points 1 day ago

An explanation for them not sending it to Germany could be that the localization team for the German region, probably being more aware of such nuances, spotted it and removed it whereas those who did the localization for other regions just didn't spot it, so it slipped through.

There could be arguments about communication between teams but, honestly, localization teams don't really need to communicate with one another so it isn't surprising that they didn't.

Most likely it actually is a "oops we fucked up" situation.