From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.bugs Subject: bug#69132: [ELPA] Remove jQuery from elpa.gnu.org Date: Thu, 22 Feb 2024 12:00:52 +0000 Message-ID: <87a5nswvwr.fsf@posteo.net> References: <87jzn6g7ep.fsf@posteo.net> <87h6iap2lz.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16267"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Corwin Brust , 69132@debbugs.gnu.org, monnier@iro.umontreal.ca To: Richard Stallman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 22 13:02:15 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rd7mJ-000428-8m for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 22 Feb 2024 13:02:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rd7ls-0007dt-9q; Thu, 22 Feb 2024 07:01:52 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rd7lj-0007dS-LF for bug-gnu-emacs@gnu.org; Thu, 22 Feb 2024 07:01:42 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rd7lj-0002BQ-AW for bug-gnu-emacs@gnu.org; Thu, 22 Feb 2024 07:01:39 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rd7m5-0005Dg-Vf for bug-gnu-emacs@gnu.org; Thu, 22 Feb 2024 07:02:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 22 Feb 2024 12:02:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69132 X-GNU-PR-Package: emacs Original-Received: via spool by 69132-submit@debbugs.gnu.org id=B69132.170860328819959 (code B ref 69132); Thu, 22 Feb 2024 12:02:01 +0000 Original-Received: (at 69132) by debbugs.gnu.org; 22 Feb 2024 12:01:28 +0000 Original-Received: from localhost ([127.0.0.1]:49373 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rd7lY-0005Bq-01 for submit@debbugs.gnu.org; Thu, 22 Feb 2024 07:01:28 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:41303) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rd7lV-0005BD-1Q for 69132@debbugs.gnu.org; Thu, 22 Feb 2024 07:01:27 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 27FC9240103 for <69132@debbugs.gnu.org>; Thu, 22 Feb 2024 13:00:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1708603255; bh=R4HYpSb7DMNxRsYPa1N6gbR7+n+Cc0gyYpOhtlsv5G8=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=hjmeVuNQVm2QTuChapTnCeygNvuQax0gQ+DUhwvLvzuW6PfYYAP7CSEkUtS4fXU83 D514wMfpt5I5AbJ+frcgKFvG7zvGmbxiqzxk6AQufyHCpyitd249tGr90CYXqmKaCZ J/BFtSsjBFTb4wKxZZD9AoWryGxbE0dP82NcglMvY3HE91EYKS6oU5O5mtpS7Tw38p OtHPyVbRbU5+IF5dkBcoaRw73rWMh5gRxQxv8v//alohF/cEuPyF8QVkj4sGtHFhZ4 D5ddNvoo3M+eAQ0DdBAreAuR5vEeSdLesx23lQiJd7Cjn8SKk4/XqRfamivSYaiKET HRC1+3RF07Xsg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TgWts4wg6z9rxY; Thu, 22 Feb 2024 13:00:53 +0100 (CET) In-Reply-To: (Richard Stallman's message of "Tue, 20 Feb 2024 21:56:24 -0500") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:280445 Archived-At: Richard Stallman writes: > > As stated: I think it is *not* possible to perform this type of > > "client-side" search without using Javascript. > > There are two fully moral ways to implement a search feature for a web > site. One is to implement it inside the web server. The other is to > communicate with a free program that the user has installed in per > computer, and could replace with any other. In this case, both options would be overkill. The search functionality does little more than just hiding a few elements from a table. In practice, it don't offer much more than using the built-in C-f search functionality, that every browser provides. [...] > We could overcome this wih a documented API that users could > optionally use for ELPA search. It would provide the package list > data in a form convenient for programs. Users could write their own > code, in Javascript or in some other language, to operate on the API > output to customize the search as they like. This would provide the > benefit you call for, in an even more general way. ELPA already has a format for listing packages in an archive, and just like with browsers, it wouldn't really provide anything that M-x list-packages and C-s doesn't already do. > (Is there a semistandard web convention for specifying API versions so > you can say, "Give me this data in the format we used in June 2022"?) > > Meanwhile, the rest of us, we who don't use that API, would not be > asked to run any code straight off the web server. > > In a later message you said this: > > > As the entire functionality it provides is just an optional, superficial > > enchantment (one that I almost never use), I don't think this is worth > > pursuing. All the ways I can imagine to achieve this would be less > > convenient hacks. > > Assuming you're talking about the same Javascript code, how about > directing users to install that code into their browsers themselves > (if they want this optional, superficial ), and giving them a > link to it. We should be talking about the same code; I am not sure what you mean by instructing users to install the code themselves? Are you talking about user-scripts? > That would avoid the moral problem of Javascript sent implicitly to > browsers, and these few users would have only a little work to do to > set it up.