Decentraleyes – Local CDN Emulation
decentraleyes.org
Decentraleyes – Local CDN Emulation
1–10 of 84 posts
Re: Decentraleyes – Local CDN Emulation
#2It's a cool idea, even if just for performance reasons. So many things come from CDNs these days, we may as well start shopping the common ones ahead of time.
But recently I learned something unexpected. Lots of extensions are terrible with their resources. On a page targeting tech-savvy people, around 1% of requests has some extension content injected into the website which requests an external font file. (info comes from CSP reports) There's so much tracking opportunity exposed through them.
Re: Decentraleyes – Local CDN Emulation
#3After clicking through several more times and ending up in a gitlab wiki, this seems to be how it works:
> It comes bundled with a fair amount of commonly used files, and serves them locally whenever a site tries to fetch them from a delivery network.
The docs, both on the site that is linked to and on the wiki is extremely bare bones, but the gist of it is that a CDN can track you through the `referer` header of the request for (say) jquery, since even if the browser has jquery already cached it will send out a request to check if the resource might have been modified.
Re: Decentraleyes – Local CDN Emulation
#4After clicking through several more times and ending up in a gitlab wiki, this seems to be how it works: > It comes bundled with a fair amount of commonly used files, and serves them locally whenever a site tries to fetch them from a delivery network. The docs, both on the site that is linked to and on the wiki is extremely bare bones, but the gist of it is that a CDN can track you through the `referer` header of the…
Would a simpler solution be to just drop referrers from CDN requests? It would probably require fewer updates to the package itself
Re: Decentraleyes – Local CDN Emulation
#5[deleted]
Re: Decentraleyes – Local CDN Emulation
#6See also LocalCDN
https://codeberg.org/nobody/LocalCDN
Its a fork from decentraleyes with some more libraries included.
Re: Decentraleyes – Local CDN Emulation
#7See also LocalCDN https://codeberg.org/nobody/LocalCDN Its a fork from decentraleyes with some more libraries included.
Interesting. However, not a part of the Recommended Extensions program. Decentraleyes is.
Re: Decentraleyes – Local CDN Emulation
#8See also LocalCDN https://codeberg.org/nobody/LocalCDN Its a fork from decentraleyes with some more libraries included.
Interesting. However, not a part of the Recommended Extensions program. Decentraleyes is.
Very true, although I do like the addition of font awesome and preprepared ublock rules in the addon
Re: Decentraleyes – Local CDN Emulation
#9I've used Decentraleyes for a while now and it works great. I would actually like to see it—or more specifically, the idea—integrated into browsers. It would improve privacy, (potentially) security, and speed at the cost of disk space.
Re: Decentraleyes – Local CDN Emulation
#10After clicking through several more times and ending up in a gitlab wiki, this seems to be how it works: > It comes bundled with a fair amount of commonly used files, and serves them locally whenever a site tries to fetch them from a delivery network. The docs, both on the site that is linked to and on the wiki is extremely bare bones, but the gist of it is that a CDN can track you through the `referer` header of the…
Would a simpler solution be to just drop referrers from CDN requests? It would probably require fewer updates to the package itself
I'm not disagreeing, but without a referrer the request would go out anyway - with decentraleyes it doesn't at all.