From: nospam.Rbernardo@iglou.Com@f135.n153.z1.binkp.net   
      
   ilar fashion, which is also beyond the   
   | scope of this FAQ. See your mail program's documentation.   
      
   1.3 What we don't post   
      
   We do not post:   
      
   	* non-binary items. Spam is deleted. Discussion is deleted. People   
   writing us about why no one discusses anything in this group get deleted.   
   Et cetera.   
    	The exceptions are the FAQ, naturally, and moderator announcements.   
   	So where should you post if you want to talk about Commodore 8-bits?   
   A good question. Refer to:   
      
   	comp.emulators.cbm   
   	comp.sys.cbm   
   	alt.c64   
      
   	All of these, in particular the first two, have active discussion.   
   Talk on them. We'd love to hear from another 8-bit fanatic.   
      
   	* binary items not relevant to the 64. UUencoded JPEGs of your pet   
   wonderdog Snotbrain whizzing on Mrs. Eagleson's petunias get deleted. And so   
   on.   
      
   	* 'warez'. Cracks, hacks, etc. are NOT allowed. The old argument   
   that 'it's 10 years ago, the copyright doesn't matter' is hogwash. Someone   
   still has the copyright, even if they're not enforcing it, and we don't want   
   to be on their lawyer's target list if they decide to enforce it suddenly.   
   (Want an example? Okay. Three words: Activision fifteen pack. Case closed.)   
   Freeware and shareware versions of products are exempt because they are   
   explicitly freely distributable, in contrast to ...   
      
   	* restricted distribution products. This is a fancy way of referring   
   to 'stuff that shouldn't be publicly distributed', and includes things such   
   as registered versions of shareware or beta tests that are not intended for   
   the public. Moreover, if there's a restriction on the software's distribution,   
   it's probably heavily copyright-protected too ... see 'warez'.   
      
   	* programs not intended for all audiences. For example, posting a   
   nudie slide show for the 64 here would not be appropriate, and it would   
   never be approved, even if it *were* in the public domain and freely   
   distributable. This is not comp.binaries.erotica.cbm. You may think this is   
   a silly thing to say, but there are some of these demos around.   
      
   	* things that don't work. Garbled submissions don't work. Make sure   
   your uuencoded file didn't get truncated. Make sure your mailer didn't eat   
   characters or add new ones, because on our end it looks like hell. IF YOU MUST   
   MAIL US YOUR POST, PLEASE see the section on 'How to post by mail' to get   
   around this problem.   
   	Most importantly, however, if it don't work, it don't post. If we   
   can't get it to run, odds are most people who read this group won't either.   
      
   	* anything we decide not to post, at our discretion. Some people have   
   claimed we're ignoring their posts because we don't like them. Tough orange   
   peels.   
      
   1.4 What happens if you post something we don't post   
      
   Nothing.   
      
   Yes, nothing. You will get no response from us, ever.   
      
   In the past, the response was to notify you that we did not accept your post,   
   and to send you some appropriate reason why. In this day and age of rampant   
   spammage and people who blindly post insulting things instead of reading FAQs,   
   that is an insurmountable task. Therefore, if you do not get a response to your   
   post WITHIN A SUFFICIENT INTERVAL and/or your post never appears on the group,   
   we did not approve it.   
      
   If you have trouble with your newsreader, and want to know if your post   
   came through, please state you want confirmation in the message body. We will   
   confirm only in cases where we have a serious posting. If you post 'why aren't   
   my messages posting somebody please respond' you will get a resounding fat   
   load of nothing returned to you. However, if there's a possible submission   
   attached to your polite and understanding request, we would be happy to tell   
   you that it got there in one piece. Do not, though, assume that a lack of   
   response indicates bad connection and therefore multiple reposting, because   
   this will not endear yourself to the moderators and collect you many four-   
   letter words. Ask first before you send that 2.5MB file again.   
      
   If you do get a message back from us, we probably just need a small extra   
   thing from you, like a description. Please read the note and comply; upon   
   your doing so, you will be the proud parent of a new post.   
      
   The phrase 'WITHIN A SUFFICIENT INTERVAL' has been cap'ed for a reason. It   
   takes time to check through a submission, first to receive it, then to test   
   it and then for the final post (if any) to percolate through the fibrous   
   wire mishmash of Usenet. Please respect the fact it may take as long as a week   
   to finish this process -- we have lives of our own, and we do this out of   
   our free time. Therefore, not seeing your post immediately does in no way   
   imply open and extremely prejudical rejection.   
      
   1.5 What happens if you post something we post   
      
   We post it.   
      
   If appropriate, we will notify you (usually 'thanks!'), but in most cases   
   you will know your post has been approved when you see it in the group. It is   
   | good form to make sure your newsreader does in fact see this group. You   
   | might also subscribe to the mailing list echo.   
      
   If you want confirmation, say so. See above for conditions on that. Remember   
   that sending confirmation messages is not guaranteed.   
      
   1.6 c.b.c courtesy   
      
   | Good things to do that make things easy for the moderators (and also, I   
   | hasten to add, make things easier on the viewing audience):   
      
   	* Use .sda or .sfx, or any other self-dearcing format. It's easy   
   for us because we don't have to crank up the dearcer. Lynx is especially bad   
   on this point, since there's so many versions, a lesson I have learned the   
   hard way with many people asking me why Ultimate Lynx doesn't understand   
   CWI's Lynx archives. (Answer: We use Lynx IV, and they're mutually   
   incompatible.) Failing that:   
      
   	* Use a standard emulator disk or tape image (compressed would be   
   nice -- .zip okay, .gz even better!). With modern code, even zipped and   
   GZipped .d64s can be handled directly on a C64, and for those mods that   
   do quick testing on an emulator, we can drop the image right in. .d64 is   
   now so ubiquitous that it has supplanted most .arc and .lnx formats as the   
   preferred method of archiving floppies and files, despite its disadvantages.   
   	  Failing that:   
      
   	* Use a standardized arc format. I like .lnx best, but can tolerate   
   .arc. I find .lzh slightly exotic and .rar even more opaque. If you post using   
   Fritz Fluegelwagen's RLE-LZW-Huffman-Lynx encoder, something three people on   
   the planet use, the chances of my hitting delete in the mailreader increase   
   exponentially.   
   	The one standard arc format you should avoid, if at all possible, is   
   ZipCode (the 1! .. 2! .. files.) These cause some irritation on my part, mostly   
   because I have to deal with four files instead of one. There are some   
   circumstances where ZipCode is needed, but most of them involve copy-   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)