• 0 Posts
  • 9 Comments
Joined 14 days ago
cake
Cake day: August 17th, 2025

help-circle

  • I’ve worked in the video game industry for a couple years and have been credited in several games. This number may actually be higher.

    It may sound crazy, but there’s a lot of people working on AAA games, usually most of them completely unrelated to game dev. Marketing, public relations, translators, 3D graphics artists, sound designers, orchestra performers, motion capture stuntmen, voice actors. Probably a few dozen managers, who have never even seen the game. Hell, some companies even credit IT staff in the game’s credits.

    That’s already a whole bunch of teams. It’s also important to mention that many third-party contractors will often be skipped from the credits. QA is very commonly outsourced (to poorer countries like Romania or Serbia) and rarely gets into the credits. You may only see 5-10 names, while in reality it was at least 100. This is true for several other fields, though mostly non-game-related, e.g., localization, promotial material, merchandise.

    I won’t disclose in what capacity, but in the past I have worked on several of Blizzard’s titles for a few months and I’m not credited anywhere. Just like at least a couple hundred other people. Not necessarily saying I should be - it was never mentioned or promised. Just highlighting that the real number of staff that worked on the game (or adjacent to the game) may be above 10k.


  • Some things are - on purpose - made easy to misuse and - by design - accessible to people, who are likely to misuse them. All this money, this supposedly cutting edge technology, and reporting to the police, but they aren’t able to tell when a child is at risk and report it as well?

    Smells like bullshit to me. More like they don’t care. I’m not so sure children should even be allowed to use chatbots in the first place. Or only allowed to use versions specifically trained for interactions with children. But of course - banning children from accessing youtube and wikipedia is a much more pressing concern.






  • Two things especially worth noting from the article.

    If you have a non-Google build of Android on your phone, none of this applies.

    This means that at least GrapheneOS will be unaffected for now. Other ROMs without gapps will be unaffected only as long as you don’t install gapps. Since Graphene has a sandbox for them, I’m assuming it’ll be fine. That is, unless Google decides to lock the bootloader entirely.

    In September 2026, Google plans to launch this feature in Brazil, Indonesia, Singapore, and Thailand. The next step is still hazy, but Google is targeting 2027 to expand the verification requirements globally.

    So most users worldwide still have at least 1.5 years until it’s implemented. Plenty of time to get a Pixel and install Graphene on it. Or to figure out some other plan.

    Don’t get me wrong - this is insane, unreasonable and horrible news for everyone. We should push back as hard as physically possible against it. However, at the very least we still have some time to figure things out before the policy rolls out.