| From a comment I noted down some time ago where the user provided a comparison between Decentraleyes and LocalCDN: - Decentraleyes has the advantage of being a "recommended" webextension which "undergoes a thorough technical security review to ensure it adheres to Mozilla’s add-on policies." - Decentraleyes' has public ownership; Thomas Reintjes. - Decentraleyes' last commit and last activity by the maintainer was 4 months ago; there are 78 open issues, and 9 merge requests with no indication of being merged in anytime soon. So I assume - LocalCDN was forked because Decentraleyes actually appears stale which is unfortunate. - LocalCDN doesn't have public ownership. - LocalCDN isn't a recommended webextension and thus updates won't undergo "thorough technical security reviews." - LocalCDN does support more assets/CDNs (which increases privacy beyond Decentraleyes) and will support more. - LocalCDN has not slipped a new permission in. Compare LocalCDN's manifest.json with Decentraleyes'. Source: https://www.reddit.com/r/privacytoolsIO/comments/fc05uh/comm... |
Source for localCDN - https://codeberg.org/nobody/LocalCDN
LocalCDN's developer is extremely pro-privacy. The extension collects nothing. Privacy policy is one sentence.
https://addons.mozilla.org/en-US/firefox/addon/localcdn-fork... https://www.localcdn.org/privacy.