🌐 Website Issue | Decentraleyes requires configuration on Chromium based browsers when HTTPS Everywhere is used #1326
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1326
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
In reality when Chromium is used with HTTPS Everywhere, the user must go to https://decentraleyes.org/configure-https-everywhere/ and disable HTTPS Everywhere for the content loaded by it so that Decentraleyes can redirect the requests into itself.
Unrelated note of future interest: IPFS Companion (listed under self-contained networks) wishes to be able to replace Decentraleyes in the future: https://github.com/ipfs-shipyard/ipfs-companion/issues/674.
Also worth mentioning that Decentraleyes doesn't work out-of-the-box if a blocker such as uBO, uM, or NoScript is being used.*
* uBO is fine if it's on Easy mode (default) or looser settings. Decentraleyes requires Scripts/XHR to function.
Also related: https://github.com/privacytoolsIO/privacytools.io/issues/1292#issuecomment-530239422 . I am going to open a meta issue to stay on track of these.
It requires configuration everywhere, including on Firefox when ublock is used.
We're thinking of removing it as per https://github.com/privacytools/privacytools.io/pull/2005#issuecomment-704006090