this post was submitted on 30 Sep 2024
358 points (96.9% liked)

Games

32918 readers
1611 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. No linking to piracy

More information about the community rules can be found here.

founded 2 years ago
MODERATORS
 

Source: https://xcancel.com/dshiatt/status/1840822267737162237

Obviously just damage control but they do seem to be "fixing it". They must've accidentally implemented a feature to get and show image from the newest news post (which is often an ad), accidentally tested and vetted that feature, and accidentally pushed it.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 69 points 2 months ago* (last edited 2 months ago) (2 children)

you don't get entire functional UI elements accurately populated with appropriate data out of a "bug". at best its a feature that was being tested internally and never would have made it past that, at worst its something that went live early.

[–] [email protected] 44 points 2 months ago

Oh whoops I accidentally built an entire ad portal and placed it onto the main page and oh no I accidentally passed it through multiple levels of code review QA and approval, then crap I deployed it to the test environment then prod

[–] Scolding7300 9 points 2 months ago (1 children)

I can see how that's a bug that it got released if the intended purpose was to do a POC and gauge the reaction from some internal testers.

But even then they were POC-ing that, which is terrible

[–] [email protected] 8 points 2 months ago

Yeah it is possible he's accurately, but misleadingly, calling it a bug because it was not meant to be deployed to production (yet). I do not think that's how he wants or expects people to take it when he calls it a "bug", though.