From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from mx1.math.uh.edu (mx1.math.uh.edu [129.7.128.32]) by inbox.vuxu.org (Postfix) with ESMTP id E44E22156F for ; Thu, 23 May 2024 05:54:31 +0200 (CEST) Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1s9zXB-00000000voR-1vD4 for ml@inbox.vuxu.org; Wed, 22 May 2024 22:54:29 -0500 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.97.1) (envelope-from ) id 1s9zXB-00000004k1Z-16HM for ml@inbox.vuxu.org; Wed, 22 May 2024 22:54:29 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1s9zX8-00000004k1Q-2U15 for ding@lists.math.uh.edu; Wed, 22 May 2024 22:54:26 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1s9zX5-00000000vnv-3oCR for ding@lists.math.uh.edu; Wed, 22 May 2024 22:54:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=wTPpYe+GIBqGA7MicoRhzTcotPvdv5vxsY3FCsxsNAo=; b=T7+3D7RO3U2iTKfeqYVE5yR4rU RcOnPc6rcY4/UrN4OhcQ3SQE+R4ufU5TBSexoNQ5nQHstlBhuK6jYKSS869JJKXeLlfiy+ax0XBTb wsadSfSPiXLT/kGIHPv1Vkb0i1z/d1a9CwJeDyTELwjUDRhVWjWeVJp53lOgVMYythgg=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s9zWy-0000aT-M1 for ding@gnus.org; Thu, 23 May 2024 05:54:19 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1s9zWv-0008ru-MN for ding@gnus.org; Thu, 23 May 2024 05:54:13 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: Updating definition of "bogus" groups? Date: Wed, 22 May 2024 20:54:03 -0700 Message-ID: <87cypd89pg.fsf@ericabrahamsen.net> References: <87zfsi9408.fsf@ericabrahamsen.net> <871q5ufb7a.fsf@eps142.cdf.udc.es> <87msoi6i3f.fsf@dataswamp.org> <87wmnlwygi.fsf@hope.eyrie.org> <878r0173si.fsf@dataswamp.org> <87pltdmf8h.fsf@hope.eyrie.org> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:SM93OWkQIj5NgoCV6F29rkgo848= List-ID: Precedence: bulk Russ Allbery writes: > Emanuel Berg writes: >> Russ Allbery wrote: > >>> I've never been clear on what this function does that I would want to >>> do and why it's bound to a key. I've only run it when I pressed b by >>> mistake, and it's never done anything. I may just be not using the part >>> of Gnus where it would be useful? > >> The docstring says "Remove bogus newsgroups." which, granted, sounds >> pretty useful. > > Historically on Usenet that means newsgroups that were deleted, so I > assume that's what it was intended to mean. > >> But then I wonder, how do they enter the *Group* buffer in the first >> place? > > Well, if it's just groups that were deleted, one either was subscribed to > them or for whatever reason had them listed and unsubscribed. > > In other news readers historically, it was common to keep a newsrc that > included every group on the server whether one was subscribed or not. In > that context, checking for bogus groups was looking for groups that you > have listed in your newsrc (possibly unsubscribed) that no longer exist. > > I guess Gnus could have the same problem? It definitely doesn't with my > settings, but I know there are a bunch of settings. What you mentioned about disappeared groups -- that they show up with a * for the article count -- is connected to how the bogus check works now: it's all around whether a group can be activated or not. You get a * when a group can't be activated, or Gnus otherwise can't figure out the group's article numbers. And the bogus check is also just asking if the group is active or not. So I guess what I'm imagining doesn't have much to do with bogosity, after all. It starts with the servers, not the groups, and asks for an explicit group list. So maybe it's just something that can live alongside the bogus check, instead of insisting on replacing it.