Decentraleyes – Local CDN Emulation
21–30 of 84 posts
Re: Decentraleyes – Local CDN Emulation
#22I'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
#23It'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 come…
Re: Decentraleyes – Local CDN Emulation
#24Re: Decentraleyes – Local CDN Emulation
#25From a security standpoint bundling is not an issue as no additional requests are made but from a speed and performance standpoint I don’t think there is much extensions like this or browser caching can do. It kind of makes me wish bundling wasn’t a thing now that we have QUIC/HTTP3 being adopted.
With all that said I am still glad to have this extension around.
Re: Decentraleyes – Local CDN Emulation
#26[1] https://git.synz.io/Synzvato/decentraleyes/-/tree/master/res...
Re: Decentraleyes – Local CDN Emulation
#27Re: Decentraleyes – Local CDN Emulation
#28After 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…