From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: John Moreno <phenix@interpath.com>,
"Karl-Johan Noren" <k-j-nore@dsv.su.se>
Subject: Re: GNKSA and Gnus
Date: 05 Jan 1998 20:54:52 +0100 [thread overview]
Message-ID: <rjn2hawvar.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: John Moreno's message of Sat, 27 Dec 97 20:07:56 -0500
[ Lars: I'd be willing to work on 10d and 10e if you are interested. ]
The GNKSA requirements seem reasonable to me. Some of the SHOULD
doesn't really apply to Gnus because of special concerns, which I
suspect is why they are SHOULD and not MUST.
> 7c Does not restrict references sensibly
I often have to manually edit the references line when posting
followups in gnu.misc.discuss in order to make INN accept it. I guess
it happens in gnu.misc.discuss because
1) The threads there are very deep.
2) There are a high fraction of Gnus users, thus none of the posters
software will restrict the header.
This is with
nntp-server-type's value is
"200 ssv2.dina.kvl.dk InterNetNews NNRP server INN 1.5.1 17-Dec-1996 ready (posting ok).\n"
I found this in the config file.
## Maximum size of a single header.
#### =()<MAXHEADERSIZE @<MAXHEADERSIZE>@>()=
MAXHEADERSIZE 1024
I would feel more safe having Gnus truncate the header, than doing it myself.
> Additionally, the software violates the `soft' GNKSA requirements
> (SHOULDs) in the following way:
> 10d Does not omit (proper) signatures from quoted text
I think Gnus should do that. The default Gnus citation handler is too
barebone, probably in reaction too the alternative citation handler
(SuperCite) which is too advanced.
> 10e Does not let the user indicate which part to followup to
This is something Gravity does, and in general a good idea. It migth
make less sense for Gnus. However, I think it would be nice if
quoting would be restricted to the currently region in the messsage
being quoted, iff `transient-message-mode' is on, and the region is
active.
> 10g Attribution line lacks Message-ID of original article
This is the only point I disagree with. The message-id is in the
references line, which should be enough. I don't think therte is
anything resembling a consensus on whether it should be included in
the attribution line as well.
> 16b Does not refuse posting an empty article
> 16d Does not refuse to post quoted text only
> 16f Does not try to prevent posting multiple copies entirely
Actually, I believe I have gotten warnings for all three of these.
> The software sports the following nice net-keeping features unmentioned
> by the GNKSA:
Command to fetch FAQ for the group.
next parent reply other threads:[~1998-01-05 19:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712280107.UAA02498@mail.interpath.net>
1998-01-05 19:54 ` Per Abrahamsen [this message]
1998-01-05 20:31 ` Russ Allbery
1998-01-05 21:29 ` Selective quoting (was: Re: GNKSA and Gnus) Per Abrahamsen
1998-01-12 22:15 ` GNKSA and Gnus Lars Magne Ingebrigtsen
1998-01-12 22:45 ` Russ Allbery
1998-02-02 18:25 ` Lars Magne Ingebrigtsen
1998-01-12 22:48 ` Hrvoje Niksic
1998-01-13 15:58 ` PATCH: Don't quote signature (was: Re: GNKSA and Gnus) Per Abrahamsen
1998-01-14 23:57 ` Kim-Minh Kaplan
1998-01-15 0:15 ` Hrvoje Niksic
1998-01-15 8:52 ` Stig Sandbeck Mathisen
1998-01-15 13:55 ` Per Abrahamsen
1998-01-15 14:16 ` Lars Balker Rasmussen
1998-01-15 14:42 ` Per Abrahamsen
1998-01-15 14:49 ` Lars Balker Rasmussen
1998-01-15 15:36 ` Per Abrahamsen
1998-01-18 13:16 ` Kim-Minh Kaplan
1998-02-08 15:18 ` Lars Magne Ingebrigtsen
1998-01-05 21:22 GNKSA and Gnus John Moreno
1998-01-05 22:02 ` Lars Balker Rasmussen
-- strict thread matches above, loose matches on Subject: below --
1998-01-04 22:04 [John Moreno <phenix@interpath.com>] " John Moreno
1998-01-08 9:14 ` Russ Allbery
1998-01-04 21:45 [John Moreno <phenix@interpath.com>] " Russ Allbery
1998-01-04 22:27 ` John Moreno
1998-01-04 23:58 ` Matt Simmons
1998-01-05 13:42 ` Robert Bihlmeyer
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=rjn2hawvar.fsf@zuse.+dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=k-j-nore@dsv.su.se \
--cc=phenix@interpath.com \
/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).