Re: Sorry for the FAQ posting
From Matthew Thomas <mpt...@spamfree.land>
· alt.ascii-art
· 21 Mar 1999 00:00 · View full thread
· report
Martin Atkins wrote: > > Sorry to post the FAQ messages again so soon, but I was just testing > the new version of my posting automator that now allows me to select > which FAQs I post and which I don't each week. Well, it's not working. The subjects are different, but the body for each message is my FAQ in each case -- the tutorials, the mini-FAQ, the old FAQ, they all turn out to be my FAQ. (Which is no bad thing, IMNSHO ... :-) > How often shall I post each one? > At the moment, I've got the documents list, the MiniFAQ, the Not > Looking Right guide and the Big FAQ for weekly posting and all the > olde FAQ files along with Colin's control codes, animations and that > Make a start tutorial by Daniel Au posting monthly. Is this OK by > everyone? IMNSHO, there actually isn't anything in the other docs which isn't covered in the main FAQ. The only drawback to the main FAQ is that it is (still) rather long, but I'm working on that. The old FAQs are an exception to my previous statement, as they cover an eclectic mix of topics, many of which are now outdated, so some of their contents aren't duplicated in the current FAQ. But OTOH, they're perhaps of historic value only now. Perhaps it would be better to stick them on the Web somewhere and link to them from the main FAQ for anyone who's interested? > I was also wondering something else... a long time ago I remember > someone saying something about posting the FAQ files with the same > somethingorother so that you only see them once until you delete them > from your newsreader when they come back again. I think that this > would be a better way of posting these, so that everyone doesn't have > to re-download it each week/month... what do you all think, and how is > it done? You're probably talking of posting articles with the same message-id -- the unique number which an NNTP server uses to identify messages (e.g. this post of yours I'm replying to has the message-id <36f...@news.vossnet.net>). Posting the FAQ with the same message-id each time is a nice idea in theory, but in practice there'd be two problems: (1) you'd confuse the hell out of Usenet readers which said `what the hey, there's two messages here with the same message-id! that's impossible!', and (2) you would need to be deeply, intimately, involved with the internal workings of your NNTP server in order to override the normal consecutive message-id numbering. Far better, I think, to allow each `regular' in the group to set their filters/killfiles/whatever to mark the FAQ as read whenever it appears, based on its subject line. Of course, if there was only one FAQ posted each week (hint hint :-) there wouldn't be nearly so much of a problem with reading the same messages over and over again. a.a-a is a fairly small group, and I really don't think a great wad of regularly posted documentation is necessary. bye -- mpt Read my columns in NewsRoom -- http://www.newsroom.co.nz/ Protect your privacy, boycott Intel -- http://www.bigbrotherinside.org/
Original message headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,4749444d68936a56 X-Google-Attributes: gidf996b,public From: Matthew Thomas <mpt...@spamfree.land> Subject: Re: Sorry for the FAQ posting Date: 1999/03/21 Message-ID: <36F...@spamfree.land>#1/1 X-Deja-AN: 457080229 Content-Transfer-Encoding: 7bit References: <36f...@news.vossnet.net> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: University of Canterbury (opinions expressed are my own) Mime-Version: 1.0 Newsgroups: alt.ascii-art
Related ASCII art in the Gallery
Explore these categories from our collection of 11,000+ artworks:
Make your own ASCII art
Turn images, text or 3D into ASCII, or draw your own – right in your browser.
About this message.
This message was posted publicly to the newsgroup
alt.ascii-art
in 1999 and is mirrored here unchanged as part of the Historic Archives – only email addresses are masked.
The artwork and text belong to their original authors: if you copy a piece, keep the artist's initials or signature intact and credit them where you can.
Are you the author? Contact us to get your posts attributed, connected to your artist profile, or removed.
Report this message
Help us keep the archive clean and accurate. Reports are reviewed by a person – nothing is changed automatically.