From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ding-owner+M39790=ml=inbox.vuxu.org@lists.math.uh.edu>
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 B1BF824811
	for <ml@inbox.vuxu.org>; Wed, 22 May 2024 14:16:46 +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 <ding-owner+M39790=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1s9kth-000000007zt-2K8E
	for ml@inbox.vuxu.org;
	Wed, 22 May 2024 07:16:45 -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 <ding-owner+M39790=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1s9kth-00000004iYa-0vGD
	for ml@inbox.vuxu.org;
	Wed, 22 May 2024 07:16:45 -0500
Received: from mx2.math.uh.edu ([129.7.128.33])
	by lists1.math.uh.edu with esmtp (Exim 4.97.1)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1s9iGT-00000004iMr-3i1C
	for ding@lists.math.uh.edu;
	Wed, 22 May 2024 04:28:05 -0500
Received: from quimby.gnus.org ([95.216.78.240])
	by mx2.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.97.1)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1s9iGK-00000007NPZ-0SgU
	for ding@lists.math.uh.edu;
	Wed, 22 May 2024 04:28:00 -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=LuduEuyvM55MvYj9oEEsi0dl9p3ypVSAN0D6XIKqZiU=; b=tqfEqdUBbpAq+06ptSGI3m8Dua
	sk5ypuGVPzEKuAeF1U3dfsOclo2avfAEjz8N9ECYlIOebAVEkgxXDacyM2soOk04UDLWv89R/ILXY
	i0opKZJ8OOxiJ8eU/oXPDPiPuYfOinx/VjEuLdFogy6Vy8YSxfkWoEi5uAW/IfTayUrU=;
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 <ding-account@m.gmane-mx.org>)
	id 1s9iGB-0001x2-Kw
	for ding@gnus.org; Wed, 22 May 2024 11:27:51 +0200
Received: from list by ciao.gmane.io with local (Exim 4.92)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1s9iG9-00093A-II
	for ding@gnus.org; Wed, 22 May 2024 11:27:45 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ding@gnus.org
From: Alberto Luaces <aluaces@udc.es>
Subject: Re: Updating definition of "bogus" groups?
Date: Wed, 22 May 2024 11:27:37 +0200
Message-ID: <871q5ufb7a.fsf@eps142.cdf.udc.es>
References: <87zfsi9408.fsf@ericabrahamsen.net>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:hEwe6VJbhxyaZrSC10ikEwB0kxg=
List-ID: <ding.gnus.org>
Precedence: bulk

> This seems like it would be more handy for cleaning up "dangling"
> groups.
>
> Does anyone have an opinion on that idea, one way or the other?

I would remove the term `bogus` altogether, it's too vague, and replace
it with something more descriptive.  This is independent from the fact
that the behaviour could be more useful, as you describe.

-- 
Alberto