• kbal@fedia.io
    link
    fedilink
    arrow-up
    84
    arrow-down
    2
    ·
    7 hours ago

    The discourse about Mozilla is ridiculous, here and most everywhere. You’ve got people taking every perceived opportunity to attack them for things they do, things they didn’t do, and things it’s imagined they might’ve done. And then another crowd of equally determined people doggedly defending them for every idiotic blunder they make, such as this one.

    Meanwhile Mozilla itself has nothing substantial to say. This is not the first time a prominent extension has mysteriously gone missing from amo with Mozilla telling us nothing about its role in the incident. @[email protected] needs to be in the discussion giving us a real explanation of what happened, why they got it wrong, and what they’re doing to improve things.

    • jol@discuss.tchncs.de
      link
      fedilink
      arrow-up
      5
      ·
      3 hours ago

      We have collectively agreed that Mozilla is a) not reviewing extentions enough, and b) reviewing too much.

    • setVeryLoud(true);@lemmy.ca
      link
      fedilink
      arrow-up
      27
      ·
      6 hours ago

      Correct, this two-sided discourse is due to a massive lack of communication on Mozilla’s part, leaving room for speculation.

      • abbenm@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        4 hours ago

        The best I can think of is that the explainer language used to justify the extension’s removal was just boilerplate language that got copy+pasted here because someone clicked the wrong button. But even that makes a mockery of the review process.

        I think “oops clicked wrong button” would be slightly more defensible, but not by much. If they truly rejected the extension for content in it that it does not have, it’s hard to see how a human could make that mistake even accidentally. But maybe there’s something I’m missing.