<HTML><FONT SIZE=3 PTSIZE=10>TYRFiction Posting Guidelines and Membership
rules<BR>
<BR>
** Guidelines for the The Young Riders Fiction Onelist **<BR>
(last updated 11 August 1999 - recent changes are marked by asterisks<BR>
in the first column)<BR>
<BR>
1. Fiction! (poetry welcome, too)<BR>
<BR>
TYRFiction, as the name implies, is for The Young Riders the sharing of<BR>
fan-written fiction. Narrative prose is the most popular format,<BR>
but scripts, poems, songs or whatever are welcome, as long as<BR>
they relate to The Young Riders.<BR>
<BR>
Anything that's not a story should be posted with the DISCUSS<BR>
topic (See below for instructions on how to use TOPICS).<BR>
<BR>
If you wish to comment on a story, TYRFiction is set to go back to the <BR>
list. So becareful of what you say. If you want to say something negative,
<BR>
please email the author privately.<BR>
<BR>
I would perfer you to send your stories this way,<BR>
Cut and paste text into your e-mail program. If it's too long to<BR>
be cut and pasted, then it's TOO LONG, and needs to be broken up<BR>
into sections. If it's not text, then it should NOT be going to<BR>
the TYRFiction.<BR>
<BR>
But if you *have* to send "attachments" then,<BR>
Send "attachments" to the TYRFiction mailing<BR>
list in .txt format. Some people may get it intact, but most people
will<BR>
NOT. Most people will simply get 95K of gibberish.<BR>
We suggest that story posts be no more than 350 lines each out of<BR>
consideration for subscribers with mail programs that limit the<BR>
size of incoming mail messages.<BR>
<BR>
For info on getting past stories or sections of stories, get the<BR>
retrieval instructions from Stacie DeShazer at
LdyLander1@...<BR>
<BR>
All stories (up to but not including the current month) posted<BR>
since the inception of TYRFiction are archived <BR>
http://www.onelist.com/community/TYRFiction<BR>
<BR>
2. Standard disclaimers<BR>
<BR>
3. Story segment length<BR>
<BR>
Due to the limitations of mailers on certain popular commercial<BR>
services we ask that you limit each story segment to 350 lines.<BR>
<BR>
4. NO REPOSTS (only revisions)!<BR>
<BR>
All post are automatically archived. Please do not repost. Rewrites<BR>
or other major revisions are ok, but if there aren't any changes,<BR>
or changes are very minor, PLEASE DON'T repost it. If you post a<BR>
rewrite of something you've posted before, please put "revised" or<BR>
"rewrite" or something like that in the subject line of each<BR>
section. When you post a revision please post all story parts,<BR>
not just what changed.<BR>
<BR>
<BR>
5. PLEASE LIMIT yourself to no more than 10 story posts per story a<BR>
day.<BR>
<BR>
Posting all of a 35 part story is sure to break the<BR>
email limit for a majority of our subscribers. (If you need to post <BR>
more than 10 parts <BR>
Please ask Stacie (
LdyLander1@...) first.)<BR>
<BR>
<BR>
6. Subject line - Do's and Don'ts<BR>
<BR>
Please do not put comments on the subject line. Please number<BR>
your story parts and include the total number if you know what<BR>
it's going to be. Part numbers should always be at the end of the<BR>
line. Please use arabic numbers (0,1,2,3,4,5,6,7,8,9,0). Don't<BR>
use roman numerals or spell out story part numbers Examples of<BR>
subject lines:<BR>
Hounds of Glory 4 of 15<BR>
Hounds of Glory 04-15<BR>
Hounds of Glory (4/15)<BR>
<BR>
If you are posting a story for someone else be sure to include<BR>
that person's name and email address (if available) in the top of<BR>
each story part.<BR>
<BR>
7. Label sex, violence, and language<BR>
<BR>
Some of our readers may be offened by certain topics one of these <BR>
topics may be<BR>
the ADULT topic. Stories containing explicit sex, graphic<BR>
violence,or profanity worse than what would be in a PG-13 movie<BR>
are acceptable for posting, but you must put 'ADULT: at the very<BR>
beginning of the Subject line of each post of a story part. Also<BR>
include a warning at the top of the story explaining why the<BR>
story needs the ADULT classification. If you're posting your story in <BR>
parts, you must put 'ADULT:' in the subject line of EACH and EVERY <BR>
part and put a warning at<BR>
the top of EACH and EVERY part IRREGARDLESS of whether that<BR>
particular part has any ADULT material. (It's just frustrating to some
<BR>
people to get caught up in a story and it turn out to have some material init
<BR>
that may offend you.)<BR>
<BR>
<BR>
8. TOPICS<BR>
<BR>
ADULT - to be used for all posts that include material that<BR>
would exceed the PG-13 movie rating.<BR>
<BR>
XOVER - to be used for all posts that involve crossing the<BR>
The Young Riders universe with other fandom universes, such<BR>
as Highlander, Star Trek, Forever Knight, X Files, etc.<BR>
<BR>
ADULTXOVER - to be used for all XOVER posts that include material<BR>
that would exceed the PG-13 movie rating (see above for<BR>
XOVER definition).<BR>
<BR>
ROUND - This is a very special topic to be used only when there<BR>
is a properly authorized and sanctioned round-robin<BR>
fiction in progress on TYRFiction. If and when we have<BR>
one of these all current subscribers will be given advance <BR>
notice.<BR>
<BR>
DISCUSS - To be used to discuss The Young Riders fanfic, comments about<BR>
someone's work, fanfic techniques, and announcing<BR>
FANZINES, and anything of a non-fiction nature. -ALL-<BR>
non-fiction posts should be posted with this TOPIC. Again, if
<BR>
you have something negative to say, please say it privately by responding to
<BR>
the person in private email. And be nice about it!!!<BR>
<BR>
TEST - If you desire to test your story posts for<BR>
the quoted-printable problem (all those stupid '='<BR>
littered all over your story). Please list as TEST.<BR>
<BR>
Other - a catch-all topic for all FICTION posts that don't fall<BR>
under any of the above classifications. <BR>
<BR>
ADMIN: This is a comand that only administration can use. If you see
<BR>
this topic, *read* it. It's immportant. I will send this out this post once
<BR>
in a while to make sure that everyone has a copy. Please read it, to refresh
<BR>
yourself with our guidelines. I will add changes as I see fit.<BR>
<BR>
==== -ALL- non-fiction posts should be posted with the DISCUSS topic. ====<BR>
<BR>
<BR>
Posting using TOPICS<BR>
<BR>
If your story qualifies for one of the above TOPICS (except the<BR>
'Other' topic) when you post each story part you should put the<BR>
appropriate TOPIC followed by a colon(:) and a space at the very<BR>
first of your Subject line. For example:<BR>
<BR>
Subject: ADULT: Shall We Dance? (1/14)<BR>
<BR>
I included 'Subject:' as an example. Different mailers may call<BR>
it different things. It is simply the title of your posts. You<BR>
shouldn't put 'Subject:' in the title of your posts.<BR>
<BR>
NOTE: Posts that fall under the scope of more than one TOPIC -<BR>
You can mark a post with more than one topic. Everything before<BR>
the colon (after 'Re:' have been discarded) is evaluated for<BR>
possible topics so you can specify more than one topic by<BR>
separating the topics by a comma. Here's an example of a multiple<BR>
TOPIC post:<BR>
<BR>
Subject: ADULT,XOVER: The Immoral Game<BR>
<BR>
<BR>
9. Formatting suggestions<BR>
<BR>
These are suggestions to help make your stories more readable.<BR>
These are NOT rules. Most of these suggestions are applicable<BR>
to any type of post to any electronic mailing list or newsgroup.<BR>
They are included here because the problems caused by poor<BR>
formatting are compounded in a story type post where you want the<BR>
reader to closely follow what you're saying instead of merely<BR>
scanning over it.<BR>
<BR>
One of the most important things to remember in this electronic<BR>
media is you _must_ pay close attention to making your stories<BR>
readable. The following suggestions should help.<BR>
<BR>
(a) Don't use special characters.<BR>
<BR>
Please don't use special characters such as combining regular<BR>
characters with umlaut/dieresis, circumflex, grave, acute<BR>
accents, right and left double-quotes. Only use ASCII<BR>
characters! If your mail program is MIME-capable it will<BR>
translate your posts to ASCII with control characters which are<BR>
very difficult to read with a mail program that is not<BR>
MIME-capable. IF you are using Microsoft Mail, turn you MIME<BR>
option OFF before posting.<BR>
<BR>
<BR>
(b) Single space everything!!<BR>
<BR>
Double spaced text is extremely difficult to read on a computer<BR>
screen, and can unnecessarily cost readers money for various<BR>
reasons (charges for mail based on size, printer charges, etc.).<BR>
Leave a blank line between paragraphs, but within paragraphs,<BR>
please single space!<BR>
<BR>
(c) Left justify everything!<BR>
<BR>
Like double spaced text, fully justified text is very difficult to<BR>
read on a computer screen.<BR>
<BR>
(d) Don't hyphenate words to break a too-long line.<BR>
<BR>
As with double spacing and full justification, hyphenated words are<BR>
much more difficult to read on a computer screen than on paper. If<BR>
you have a long word that won't fit on the line, just let that line<BR>
be short, and take the word to the next line.<BR>
This also applies to e-mail addresses. If an address is too long<BR>
to fit on one line, it's somewhat common to split it at @ ., but<BR>
it's really preferable put the whole thing on a new line.<BR>
<BR>
(e) Limit your Line length<BR>
<BR>
Ideally, each line of text should be NO MORE THAN 72 characters.<BR>
It makes things much easier to read and the lines don't break<BR>
funny (full line, one word, full line, two words) when your story<BR>
hits our mailbox. Also, MIME-capable mailers will translate your<BR>
post into a message with equal signs (=) or (=20) at the end of<BR>
all the too line lines. It makes a very ugly mess on this end.<BR>
Not to mention (again) that shorter lines makes your prose<BR>
much,much more readable. Our eyes are trained to be comfortable<BR>
with white space, look at the borders on a page in a book. The<BR>
more readable your story appears then it will be less likely<BR>
that someone will put it down before you (the author) has<BR>
managed to capture another victim, Er, reader.<BR>
Be particularly careful if you type a story in a PC or MAC word<BR>
processor (such as MS-Word) and upload it for posting. If not<BR>
saved properly, your paragraphs may be saved as single lines,<BR>
causing the over 80 characters per line problem in a big way.<BR>
'Textedit', the default editor on Suns is -notorious- for not<BR>
putting hard returns at the end of lines. You -must- put them in<BR>
yourself.<BR>
<BR>
(f) the TAB key<BR>
Avoid the TAB key. Different systems treat tab characters<BR>
differently, which can cause very strange, and undesirable, results<BR>
on different computers. If you want to indent or center something,<BR>
use spaces instead of tabs.<BR>
Many people avoid this problem entirely by not indenting anything.<BR>
<BR>
(g) Quotes<BR>
<BR>
To indicate that a character is thinking something, rather than<BR>
speaking, you might want to consider using something other than<BR>
standard double-quotes ("). Many people use single-quotes ('),<BR>
asterisks (*), or angle brackets (<> or ><).<BR>
<BR>
(h) New speakers<BR>
<BR>
There is an extremely important, but often ignored, grammatical<BR>
rule that whenever a different person starts speaking (or thinking)<BR>
something, you start a new paragraph.<BR>
<BR>
(i) Check spelling & grammar<BR>
<BR>
This one is pretty basic. Poor spelling and/or grammar makes<BR>
things very difficult to read and can alienate your audience.<BR>
Please, Please, if you have a spell-checker program USE it.<BR>
<BR>
(j) Electronic writing conventions<BR>
<BR>
Since we're using only letters, numbers, and the more basic special<BR>
characters to write things for the lists, certain conventions have<BR>
evolved to help get around that.<BR>
To emphasize a word that would normally be italicized, put<BR>
*asterisks* around it.<BR>
To indicate underlining, put an _underscore_ before and after the<BR>
word/phrase.<BR>
And, most importantly, don't yell unless you mean to. TYPING IN<BR>
ALL CAPS IS THE WRITTEN EQUIVALENT OF YELLING AND IS VERY ANNOYING,<BR>
AS WELL AS DIFFICULT TO READ.<BR>
<BR>
<BR>
10.OTHER<BR>
<BR>
To Subscribe go to
http://www.onelist.com/subscribe.cgi/TYRFiction or <BR>
send a message to Stacie (
LdyLander1@...)<BR>
<BR>
To change your subscription options to stop receiving the list of a<BR>
period of time (i.e. for a vacation or finals week): Send a message to <BR>
Stacie (
LdyLander@...) or go to the
http://www.onelist.com/ and mark the
<BR>
no-mail box for TYRFiction. To start recieving mail again from TYRFiction <BR>
then repeat procedure.<BR>
<BR>
To change your subscription options to receive the list in a daily<BR>
digest: send mail to Stacie (
LdyLander1@...) or <BR>
go to
http://www.onelist.com and click on the digest box. To stop recieving
<BR>
digests repeat prodcedure.<BR>
<BR>
To Unsubscribe: send mail to Stacie (
LdyLander1@...) or go to <BR>
http://www.onelist.com/ and click onthe unsubscribe box.<BR>
<BR>
Note: DO NOT send mail to the list to unsubscribe.<BR>
<BR>
It may seem that your unsubscribe didn't take effect because you are <BR>
still<BR>
getting posts. There is probably a backlog of messages in TYRFiction's<BR>
queue that were posted before you sent the unsubscribe command. Those <BR>
will<BR>
continue to come until it gets to the timestamp when you unsubscribed.<BR>
This can take several hours or might even take up to 24 depending on<BR>
how backed up everything is.<BR>
<BR>
~~~~~~~~~~~~~~~<BR>
Stacie DeShazer <BR>
(List Owner)<BR>
StacieMairi@... <BR>
<BR>
<BR>
All past posts can be found at
http://www.onelist.com/listcenter.cgi?listname=TYRFiction&yy=36325<BR>
<BR>
Thanks,<BR>
Stacie <BR>
"List Mommy"<BR>
</HTML>