• 0 Posts
  • 4 Comments
Joined 2 years ago
Cake day: July 2nd, 2023
  • zkfcfbzr@lemmy.worldtoFirefox@lemmy.ml•Mozilla removes uBlock Origin Lite from Addon store. Developer stops developing Lite for Firefox; "it's worrisome what could happen to uBO in the future."English
    0·
    9 months ago

    Reviving a long-dead thread for a relevant update, in a top-level post because you deleted all of your replies in the thread where it was relevant.

    Mozilla did reply to my email asking for clarification on their Fakespot privacy policy, and whether they collect or sell user data, as we were discussing - though that reply took them four weeks. Their response in full:

    “”" Hello,

    Thank you for contacting Mozilla and for your question. At this time, Fakespot does not sell or share any user data pursuant to any applicable privacy laws. The only data we share outside of Mozilla are generalized aggregated metrics with service providers who make Faksepot run to help us with logging and debugging issues to provide an uninterrupted experience for our customers, and we do not share this data for monetary gain. We are in the process of updating our privacy policy for additional clarity on all the points referenced in your email.

    We trust this answers your questions and thank you again for reaching out.

    Kind regards, Mozilla “”"

  • zkfcfbzr@lemmy.worldtoFirefox@lemmy.ml•Mozilla removes uBlock Origin Lite from Addon store. Developer stops developing Lite for Firefox; "it's worrisome what could happen to uBO in the future."English
    0·
    10 months ago

    My own reading of the situation on the developer’s GitHub is unfortunately that the review by Mozilla is indeed completely inaccurate in every way. No way to even read it as a “Each side has their own story” type of thing since they reproduce Mozilla’s emails verbatim. They seem just materially incorrect. The source files referenced by the emails are visible on the same GitHub account, along with their complete histories showing no changes at all - the issues referenced don’t and never did exist.

    The only redeeming thing I can find is that the dev (ambiguously) seems to have never replied to the email from Mozilla about the issues, and so Mozilla was never made aware that there was an issue with the review that needed fixing. They seem to have done this because they perceived the process as hostile and not worth engaging with, which… fair, I guess.