• @M_Reimer
    link
    English
    14
    edit-2
    1 year ago

    deleted by creator

    • @KelsonV
      link
      English
      41 year ago

      Yeah, this really needs to have

      1. A clear, user-visible list of which domains are quarantined
      2. A clear, user-visible explanation of why those domains are quarantined
      3. A way to say “Fine, but I want to allow this extension on this site” like the location and camera preferences, rather than simply turning the entire feature on and off.
  • @[email protected]
    link
    fedilink
    English
    141 year ago

    I was also a little concerned when I saw this in the release notes earlier today. Why not make this opt-in (with a warning explaining the reasoning behind it) rather than opt-out via about:config?!

  • @[email protected]
    link
    fedilink
    English
    121 year ago

    Seems to be much ado about nothing currently. Even in the release notes it clarified that this feature is not yet included and the quarantine list will be shared once ready (and will at first be mostly test domains). The blog seems to be wildly speculating on its intended use and possible impacts given the knowledge currently available

    • @voracread
      link
      English
      91 year ago

      Why? This is like some authoritarian clause in a new law being introduced with a reassurance that it will only be used for national security purpose. I feel the author is correct until more explanation is given. Even then it does not look good to me.

  • maëlys
    link
    fedilink
    English
    3
    edit-2
    1 year ago

    does using librefox help circumvent this ? also we got too comfortable with corps . do we need to build our own naviagtor now ?

  • 𝒍𝒆𝒎𝒂𝒏𝒏
    link
    fedilink
    English
    -21 year ago

    Won’t people just see this error, do a quick search and end up disabling this in the about:config?

    Seems like a waste of dev time