From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/13398 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: [John Moreno ] Re: GNKSA and Gnus Date: 04 Jan 1998 12:02:23 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035152773 9108 80.91.224.250 (20 Oct 2002 22:26:13 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:26:13 +0000 (UTC) Cc: John Moreno , "Karl-Johan Noren" Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.8/8.8.8) with ESMTP id CAA24244 for ; Sun, 4 Jan 1998 02:52:55 -0800 Original-Received: from farabi.hpc.uh.edu (farabi.hpc.uh.edu [129.7.102.2]) by xemacs.org (8.8.5/8.8.5) with ESMTP id EAA16099 for ; Sun, 4 Jan 1998 04:53:23 -0600 (CST) Original-Received: from sina.hpc.uh.edu (lists@[10.1.1.1]) by farabi.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id MAN14970; Thu, 1 Jan 1998 12:45:51 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 04 Jan 1998 04:37:48 -0600 (CST) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by sina.hpc.uh.edu (8.7.3/8.7.3) with SMTP id EAA20699 for ; Sun, 4 Jan 1998 04:37:40 -0600 (CST) Original-Received: (qmail 27253 invoked by uid 504); 4 Jan 1998 10:37:29 -0000 Original-Received: (qmail 27250 invoked from network); 4 Jan 1998 10:37:24 -0000 Original-Received: from xyplex09.uio.no (HELO sparky.gnus.org) (129.240.154.29) by claymore.vcinet.com with SMTP; 4 Jan 1998 10:37:23 -0000 Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id MAA13614; Sun, 4 Jan 1998 12:04:55 +0100 Original-To: ding@gnus.org X-Mailer: Quassia Gnus v0.19/XEmacs 19.15 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ Subject: Re: GNKSA and Gnus Date: Sat, 27 Dec 97 20:07:56 -0500 From: John Moreno To: "Karl-Johan Noren" , "Lars Magne Ingebrigtsen" Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Karl-Johan Noren wrote: [...] >> Also did you send a copy of the review to the author? > >Nope - but I guess I should have, and I don't have the review >available on the computer I use right now (I'm not sure it's >still on my Unix account either). Gnus have a homepage at > > http://www.gnus.org/ > >though, I think. Well here it is: ============================================================================ GNKSA Evaluation Form v2.0 Product Name : Gnus Product Version : 5.3 Tested on platform : Unix/GNU Emacs 19.34 Available for platforms: Emacs 19 Evaluation date : December 10, 1997 Evaluated by : Karl-Johan Norén Summary ======= Regarding the strict GNKSA requirements (MUSTs), this software: [ ] PASSES, hence can from now on proudly carry the Seal. [X] FAILS on the following points: 7c Does not restrict references sensibly 16c Does not warn when posting quoted text only Additionally, the software violates the `soft' GNKSA requirements (SHOULDs) in the following way: 10d Does not omit (proper) signatures from quoted text 10e Does not let the user indicate which part to followup to 10g Attribution line lacks Message-ID of original article 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 The software sports the following nice net-keeping features unmentioned by the GNKSA: Fully customisable via elisp. Support for NoCeM (I haven't tested this, though). Asks if posts are to be sent to unknown groups (ie groups not present on the newsserver). Good easily customisable threading, and it's easy to fetch older articles in the thread. Allows colouring of quoted text, signatures, new text, headers etc. Additional Comments: I haven't been able to test the 998-character limit on references lines, it does however wrap the reference line. Checklist ========= (M)UST / (S)HOULD 1) Displays all essential header information Software clearly displays: [Y] a) Article's author (From) M [Y] b) Article's Subject M [Y] c) List of groups posted to (Newsgroups) M [Y] d) Where (and how) to direct followups (Followup-To) M [Y] e) Where to reply to if not the From-address (Reply-To) M [Y] PASS: Satisfies all MUSTs M 2) Provides clear, separate commands for new posting, followup, and e-mail reply [Y] a) for posting a new article M [Y] b) for posting a followup article M [Y] c) for replying by e-mail M [Y] d) Uses standard terminology S [Y] e) Avoids ambiguous terminology S [Y] PASS: Satisfies all MUSTs M 3) Provides cross-posting functionality [Y] a) Allows specifying multiple groups M [Y] b) Warns about, or prevents, posting to large numbers of groups S [Y] c) Strongly encourages setting Followup-To: on large crossposts S (`Y' if large crosspostings are disallowed) [Y] PASS: Satisfies all MUSTs M 4) Allows users to change essential headers [Y] a) Allows editing Subject at all times during composition M [Y] b) Allows specifying new Subject of at least 70 characters M [Y] c) Allows setting "Followup-To: poster" M [Y] PASS: Satisfies all MUSTs M 5) Ensures followups and e-mail replies contain a correct Subject [Y] a) Prepends "Re: " if (and only if) not already present M [Y] b) Preserves entire original Subject (modulo minor repairs) M [Y] PASS: Satisfies all MUSTs M 6) Directs followups to the correct newsgroups [Y] a) Posts to groups in Followup-To if present M [Y] b) Initiates e-mail reply rather than a followup posting on "Followup-To: poster", clearly informing the user M [Y] PASS: Satisfies all MUSTs M 7) Make sure followups contain valid References [Y] a) Creates References header with Message-ID of original article as the last element M [Y] b) Includes last three References from original M [N] c) Ensures References will fit in 998 characters M [Y] d) Keep as many References from original as fit S [Y] e) Does not propagate broken Message-IDs in original References S [N] PASS: Satisfies all MUSTs M 8) Direct e-mail replies to the correct address [Y] a) Uses Reply-To if present M [Y] b) Uses From address otherwise [Y] PASS: Satisfies all MUSTs M 9) Allow the user to change her mind about whether to post or mail (or do both) and behave if doing both [Y] a) Allows users to change their mind and mail rather than post after having initiated a followup message M [Y] b) Allows users to change their mind and post rather than mail after having initiated a reply message M [Y] c) Does not offer both posting and mailing as default behaviour M [Y] d) Inserts a notification that the message was posted as well as mailed in the e-mail copy when both posting and mailing a followup article S [Y] PASS: Satisfies all MUSTs M 10) Provide adequate quotation and attribution facilities [Y] a) Allows including quoted original M [Y] b) Clearly distinguishes quoted material M [Y] c) Prefixes quoted material with `>'/`> ' S [N] d) Omits correctly delimited signatures from quoted material S [N] e) Provides a means of indicating which part(s) to followup to S [Y] f) Attribution line containing original author precedes quotes M [N] g) Attribution contains Message-ID of quoted article S [Y] PASS: Satisfies all MUSTs M 11) Provide a user-specified "Subject: " header [Y] a) Requires non-empty, user-specified Subject for new articles M [Y] b) Refuses posting articles without, or with an empty, Subject M [Y] c) Does not provide default Subject if user did not set one M [Y] d) Allows changing the Subject at any time while editing M [Y] PASS: Satisfies all MUSTs M 12) Provide a valid "From: " header [Y] a) Sets "From: " header to syntactically valid e-mail address M [Y] b) Refuses posting articles without a syntactically valid "From: " header M [Y] c) Uses correct e-mail addresses (valid and belonging to the user) only, as far as it can possibly know S [Y] PASS: Satisfies all MUSTs M 13) Allow users to both cancel and supersede their own articles (and _no_ others!) [Y] a) Allows cancelling articles S [Y] b) Allows superseding articles S [Y] c) As far as possible, does not allow cancelling or superseding other peoples' articles M [Y] d) Uses standard terminology S [Y] PASS: Satisfies all MUSTs M 14) Try to respect the 80-character line-length convention [Y] a) Articles are posted as edited, with linebreaking intact S [Y] b) Warns about lines over 80 characters S [Y] c) Does not refuse to post articles containing long lines S [Y] d) Allows rewrapping quoted text S [Y] e) Enforces formatting requirements on article after external editing (`Y' if there is no support for external editors) S [Y] PASS: Satisfies all MUSTs M 15) Separate signatures correctly, and don't use excessive ones [Y] a) Uses (and enforces) standard signature delimiter S [Y] b) Warns against or refuses to use excessive signatures S [Y] PASS: Satisfies all MUSTs M 16) Try to prevent obvious user errors [Y] a) Warns when attempting to post empty articles M [N] b) Refuses posting empty articles S [N] c) Warns when post articles containing quoted material only M [N] d) Refuses posting quoted-text-only articles S [Y] e) Warns against posting multiple copies (if possible at all) M [N] f) Prevents multiple posting entirely S [N] PASS: Satisfies all MUSTs M 17) Post human-readable articles unless ordered otherwise [Y] Does not (and can not) encode or encrypt articles unless on explicit user demand M [Y] PASS: Satisfies all MUSTs M 18) Provide self-protection [Y] Allows filtering out annoying articles (killing) S [Y] PASS: Satisfies all MUSTs M 19) Be kind to servers, leave room for others [Y] a) Does not unnecessarily open multiple connections M [Y] b) Does not generate excessive server load otherwise M [Y] PASS: Satisfies all MUSTs M ------- End of forwarded message -------