리뷰 232개
- 5점 만점에 5점AloeVera17 님, 4년 전
- 5점 만점에 5점Firefox 사용자 16789234 님, 4년 전
- 5점 만점에 5점Firefox 사용자 15107860 님, 4년 전
- 5점 만점에 5점WhatchaLookingAt 님, 4년 전
- 5점 만점에 5점LEoREo_2247 님, 4년 전
- Amazing work. Only problem I have is with the donation stuff that involves non traditional methods (like pay-pal) due to privacy reason. This project definitely deserves finance so it can extended.
I would add another point at "diffrences between LocalCDN and Decentraleyes" great documentation. Very eassy to understand.
It saddened me to read that Mozila flags for add-ons are so superficial.개발자 답글
4년 전에 게시됨Thank you very much for your great feedback. I'm glad you like the extension and are happy with it :) - 5점 만점에 5점Mistermind 님, 4년 전
개발자 답글
4년 전에 게시됨There could be various reasons:
* strong Same-Origin-Policy (serverside)
* crossorigin/integrity attributes (serverside)
* ServiceWorkers (serverside)
* missing frameworks (LocalCDN)
You can test a website online or manually:
* https://www.localcdn.org/test/check
You can always report the website as an issue at codeberg or by e-mail. Then I could see what the problem is and improve the extension:
* https://codeberg.org/nobody/LocalCDN/issues
* https://www.localcdn.org/contact개발자 답글
4년 전에 게시됨Thanks for your feedback :)
I have created an issue on Codeberg and already made a few adjustments. I would be happy if you would test it :)
https://codeberg.org/nobody/LocalCDN/issues/257- 5점 만점에 5점TheConservativeCrocodile 님, 4년 전AWESOME!
Much better than Decentraleyes, because it replaces 10x more CSS/JS libraries.
I've been using Decentraleyes for 2 months and it has replaced only 800 libraries in that time. LocalCDN on the other hand, has replaced 800 libraries within 2 days!
Keep up the fantastic work! :)개발자 답글
4년 전에 게시됨Thank you for the great feedback. I'm very happy if you are satisfied with the extension :) 개발자 답글
4년 전에 게시됨I'm glad if you like the extension :) Thank you. I wish you the same (belatedly) and a good start into the new year ;)- Unfortunately breaks some websites when loading a different version of certain frameworks than what the website requires. The developers should allow an option to disable these broken versions individually instead of turning off the extension for the entire website.
Good for most websites but not all개발자 답글
4년 전에 게시됨Thanks for your feedback. Normally upgrading within a major line (v5.x or v4.x) isn't a problem. But unfortunately there are exceptions, e.g. jQuery. I could add a option to disable upgrades, but if you load a framework from a CDN, you can load more from there. There you can also use the whitelist directly and disable the extension for a domain. It would be great if you report these sites, then I can look at it and improve the extension.