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. @mozilla@mozilla.social 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.
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.
True in a way. However, there is a rather large collection of speculation on the Internet that is quite an undertaking to correct. And a large population of people and bots willing to speculate. Also, having once been speculated, each speculation takes on a life of its own. If it gets much more substantial, forget Skynet, we’re busy creating Specunet and its sidekick Confusionet – an insidious duo.
We’ve made the hard decision to end our experiment with Mozilla.social and will shut down the Mastodon instance on December 17, 2024. Thank you for being part of the Mozilla.social community and providing feedback during our closed beta. You can continue to use Mozilla.social until December 17. Before that date, you can download your data here (https://mozilla.social/settings/export), and migrate your account to another instance following these instructions (https://support.mozilla.org/en-US/kb/mozilla-social-faq).
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. @mozilla@mozilla.social 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.
We have collectively agreed that Mozilla is a) not reviewing extentions enough, and b) reviewing too much.
Correct, this two-sided discourse is due to a massive lack of communication on Mozilla’s part, leaving room for speculation.
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.
True in a way. However, there is a rather large collection of speculation on the Internet that is quite an undertaking to correct. And a large population of people and bots willing to speculate. Also, having once been speculated, each speculation takes on a life of its own. If it gets much more substantial, forget Skynet, we’re busy creating Specunet and its sidekick Confusionet – an insidious duo.
Gotta love circular reporting.
Mozilla.social no longer exists, Mozilla took it down
Yep, which further highlights the problem: @mozilla@mozilla.social 🔗 https://mozilla.social/users/mozilla/statuses/113153943609185249