Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Updating definition of "bogus" groups?
Date: Tue, 21 May 2024 15:47:19 -0700	[thread overview]
Message-ID: <87zfsi9408.fsf@ericabrahamsen.net> (raw)

Hi all,

In bug#60078[1], there's some discussion about Gnus's check-bogus-group
functions and whether they're buggy, or what exactly they're supposed to
do, and eventually what "bogus" actually means.

Near as I can tell, "bogus" once upon a time meant something very
specific in the Usenet world, but that was 20+ years ago, and it's no
longer a term of art. If you look at `gnus-check-bogus-newsgroups', the
20-year-old code that determines if a newsgroup is bogus is:

(unless (or (gnus-active group) ; Active
	    (and (gnus-info-method info)
		 (not (gnus-secondary-method-p
		       (gnus-info-method info))))) ; Foreign
  ;; Found a bogus newsgroup.
  (push group bogus))

So if a group is active, or if it belongs to a method that isn't a
secondary method, then it isn't bogus.

That seems like an odd and arbitrary criteria for weeding out groups.

Based on what I think "bogus" once meant (just that a newsgroup is being
superseded, or otherwise discouraged, and dropped from servers' lists),
it seems like a more reasonable update of the intention would be:

A group is bogus if it belongs to a select method that has a
`gnus-request-list' function, but the group itself doesn't appear in the
list.

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?

Thanks!
Eric


[1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60078



             reply	other threads:[~2024-05-21 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 22:47 Eric Abrahamsen [this message]
2024-05-22  9:27 ` Alberto Luaces
2024-05-22 14:23   ` Emanuel Berg
2024-05-22 17:25     ` Russ Allbery
2024-05-23  0:47       ` Emanuel Berg
2024-05-23  2:30         ` Russ Allbery
2024-05-23  3:54           ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfsi9408.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).