From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: Condition to link to javascript code? Date: Fri, 23 Dec 2016 14:40:18 +0100 Message-ID: References: <87eg19uc8y.fsf@gnu.org> <87pokpnn7b.fsf@bzg.fr> <87lgvc8hrp.fsf@bzg.fr> <878trb517w.fsf@bzg.fr> <87oa05h66j.fsf@gmx.us> <87y3z8feig.fsf@gmx.us> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1482500452 19526 195.159.176.226 (23 Dec 2016 13:40:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2016 13:40:52 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 23 14:40:48 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKQ5W-00048k-9R for ged-emacs-devel@m.gmane.org; Fri, 23 Dec 2016 14:40:46 +0100 Original-Received: from localhost ([::1]:39267 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKQ5a-000246-U3 for ged-emacs-devel@m.gmane.org; Fri, 23 Dec 2016 08:40:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45688) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKQ5U-000241-5C for emacs-devel@gnu.org; Fri, 23 Dec 2016 08:40:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKQ5P-0000UJ-An for emacs-devel@gnu.org; Fri, 23 Dec 2016 08:40:44 -0500 Original-Received: from [195.159.176.226] (port=39664 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cKQ5P-0000Tl-3v for emacs-devel@gnu.org; Fri, 23 Dec 2016 08:40:39 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cKQ5F-0002Nb-M0 for emacs-devel@gnu.org; Fri, 23 Dec 2016 14:40:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 53 Original-X-Complaints-To: usenet@blaine.gmane.org In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:210752 Archived-At: Am 22.12.2016 um 20:56 schrieb Richard Stallman: > Could you put some JS code into the page that would give the user > a way to specify a different URL for klipse.js? Perhaps that could > be stored in a cookie or something else in the browser. You could do that by rewriting the page into the form that is then ultimately displayed in the browser. But I don't consider that a good solution as the user doesn't know what's going to happen before trying to use the file (and not at all if the respective cookie already exists, which the user might have forgotten about or has been dropped in from somewhere). > Maybe it is a good solution, but I can't tell from what you sent. > Can you show me a clearer description of what features this addon > actually has? Basically, it intercepts requests to several CDN and delivers those files from a local repository (delivered with the extension) instead. You can configure it to block requests to those CDN altogether even when the requested file is not locally available. It doesn't cache anything not available from the repository (and also doesn't use anything in Firefox's cache). That's a good thing in a way, but limits you to the selection of locally available files that come with the extension. Creating a custom repository is listed as a "planned feature", though. > > Protects you against tracking through "free", centralized, content > > delivery. It prevents a lot of requests from reaching networks like > > Google Hosted Libraries, and serves local files to keep sites from > > breaking. Complements regular content blockers. > > in regard to klipse.js. I've not looked into it in much detail, but I think that klipse.js is not yet included in decentraleyes, so it would either block the request totally or allow it to go to the Google API CDN, depending on configuration. The more permanent solution for this problem would be to use a local filtering/blocking (like privoxy, GPLv2). It would also need to cache CDN files, which privoxy doesn't do; it must be chained with a caching proxy (like squid, GPLv2) to do that. If it would then download missing files via TOR it could completely eliminate tracking via CDN. It would sure be a nice thing to have something like that in a ready-to-use fashion. > Also, is Decentraleyes free software? What is its license? MPL-2.0 according to the home page. -- Achim. (on the road :-)