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.

  • underisk@lemmy.ml
    link
    fedilink
    English
    arrow-up
    71
    arrow-down
    2
    ·
    edit-2
    1 month ago

    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.

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      English
      arrow-up
      45
      arrow-down
      1
      ·
      1 month 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@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 month ago

      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

      • underisk@lemmy.ml
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 month 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.