A83: Re: Maillist ediquitte/some other stuff

[Prev][Next][Index][Thread]

A83: Re: Maillist ediquitte/some other stuff


People lose interest in a message after 3 or 4 lines... try to send multiple
messages or shorten the existing one.
i hit reply simply because it is faster for me.  I like to be able to read
previous posts on the same train of thought also.  It pisses me off when
someone replies to a message, that i deleted a few days ago and have no idea
wtf the guy is talking about.

Mailing list etiquitte will never prevail, because someone is always going
to get mad, and a chain reaction of anger will ensue many disagreeable
threads.

Also, DO NOT COMPLAIN ABOUT THE LIST... remember you are here because YOU
WANTED TO BE
you SUBSCRIBED, and if you have a problem with the content then you can
UNSUBSCRIBE easily.

-Harper Maddox

jerky@ebicom.net
IRC nick: Geori
ICQ: 1214597

-----Original Message-----
From: Eric Shattow <ribbit@uss.net>
To: assembly-83@lists.ticalc.org <assembly-83@lists.ticalc.org>
Date: Saturday, September 12, 1998 2:43 PM
Subject: A83: Maillist ediquitte/some other stuff


>
>first off, i'm new to assembly programming (much less on calculators), and
i don't like my mailbox being flooded with maillist messages, so i
>have been recieving the messages in digest mode. It's really great, and you
all should try it sometime, provided that the users of the list
>follow some basic "niceness" to everyone else...  well they haven't so i've
made some guidelines i hope you all follow:
>- when replying, only quote the first 5-15 lines of the original message,
or selectivley quote it.
>  (quoting a 450 line message just sucks. [eg. in one digest message i have
seen a quoted message in which there are at least 50 lines like
>this: ">>>>>>> inc hl ; We'll waste space here to gain some speed". this is
very annoying to me because i've already read that message, the
>message that quotes it, the message that quotes the message that quotes it,
the message that quotes the message that quotes the message that
>quotes it, ad. inf.] )
>- this has been said before, but don't put more then a 4-5 line piece of
ascii art in your message unless it has some relevance to your
>subject.
>- don't send stupid messages (like "you suck"), and don't reply to stupid
messages. let the maillist admin deal with retarded underserving
>pond scum.
>- the "Subject:" field is there for a reason in an email;  use it!
>  (a lot of messages that change topic in mid-thread have the same
subject... very annoying to both normal and digest recieving subscribers)
>- source code in the message is nice, and i like to see it, but like...
well, if possible; include an ftp or http link where you can
>view/download it online. even if it is besides the source in the email, a
internet link where the source can be downloaded helps a lot if you
>don't want to copy + paste to a new file and then edit out any extreneous
line feed characters, etc.
>- the easiest way to reply to a message is to reply, tell your email
program to quote the original text, and then delete everything to be
>forwarded that doesn't have direct relevence to your message.  use an
elipsis "..." on a line to indicate where you cut out text in the
>middle, a pound sign "#" for text you cut out at the beginning of the
quoted text, and a tilde "~" for text you cut out at the end (i use this
>a lot with those listbot and juno adv.s because adv.s look ugly when you
quote them, like you don't know how to use an email client properly).
>
>
>
>okay, the other stuff:
>
>i'm making an email program for the TI-83 (and maybe other calcs when i
have time).  i don't know where to start about making the word
>processor part.  i can't decide if i should remap the TI letter
designations and make it more qwerty-like or what ever... it will support
>upper/lower case though, and all of the 101-key keyboard ascii characters.
it's gonna be more word processor than email client, but it will
>support the cable/IR/RF links (RF link is gonna be worked out soon, i hope)
and Calculator ID designations (like email addresses... only
>different).
>
>what should i start out with?   i'd like to manage the power, so that i can
do a direct input in a sort of reduced power mode (_getkey just
>won't cut it), but i don't know how to do this. Also, some sort of word
based compression would definately help, if it were small enough to
>implement... i hope one of you people can help me out with compression, i
am only familiar with the concepts and not designing the algorithms
>and using them.  Does anyone know exactly what causes the calc to screw up
in SOS with rom v1.0800 with the 2nd+ON thing?  I want to avoid
>that, and maybe patch sos myself because i've been making my calc reset way
too much by accident. heh.
>
>well i appreciate you reading my message, and i hope you all follow the
guidelines at top for the sake of digest subscribers ;o]    (some
>input into my ti e-mail program inquiries would be very much appreciated
also).
>
>Peace.
>
>-Rade
>
>
>--
>Eric Shattow aka "RadonEatr" [ribbit@uss.net]
>http://members.uss.net/ribbit/
>Student
>New Trier High School
>
>