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.