Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
decentraleyes
decentraleyes
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Microsoft has acquired GitHub. Decentraleyes has left GitHub. Welcome to its new home!

To participate, please register, or sign in with an existing GitLab.com, Bitbucket, or GitHub account.

Past contributions on GitHub? Be sure to reclaim your Comments, Issues, and Pull Requests.

  • Thomas Rientjes
  • decentraleyesdecentraleyes
  • Issues
  • #413

Closed
Open
Created May 04, 2020 by User486375@User486375

Is configuring HTTPS Everywhere relevant to the average user anymore?

Hello. Your guide found here was introduced to avoid conflict errors on chromium based browsers, of which every user used to be notified of. Seeing as chromium based browsers now seem to suppress conflict errors unless the user specifically enables "Collect errors" on a per extension basis, isn't this guide now irrelevant? Unless of course it affects blocking/interception entirely if decentraleyes isn't the most recently installed extension, rendering decentraleyes useless unless the fix is applied. In which case this FAQ answer should be changed to something more adequate considering conflict errors are no longer part of the issue.

I also can't seem to even reproduce any conflict errors with Collect errors enabled in both decentraleyes and HTTPS Everywhere currently. Though I only tried your configuration page and stackoverflow.com.

Edited May 04, 2020 by User486375
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None