C
curious
kony said:Please adjust your newsreader to use shorter line lengths.
80 characters is often considered the max but lower tends to
be more readable. That may result in more replies, too.
Yes the drop can effect a computer, but on most (better) PSU
several stages of capacitor filters will buffer it enough.
you might want to run some stress tests on CPU, memory,
video (if you're a gamer) to verify stability while the
heavy applicances like an AC unit are power cycling.
You might also consider a separate circuit for the AC, or
the computer, or even an online UPS (with line conditioner
built-in) if it continues to concern you.
Thanks for the replies, everyone. I'm getting this Belkin UPS:
http://catalog.belkin.com/IWCatProd...t_Id=&Section_Id=77&pcount=&Product_Id=186802
Hope it works.
Now regarding the fact that I am using "quoted printable" which results in long line lengths... the author of my newsreader (Colin Wilson) actually recommended that we use the "quoted printable" (or "flowed") format. Here's a message he posted to a thread who's subject was the splitting of really long URLs:
"Everyone seems to be confusing the length of 'sent' lines and the
length of lines that their newsreaders display.
Wrapping lines - to 72 characters or whatever before sending them
should be completey unnecessary. However, because the NNTP protocol
restricts lines to around 990 characters, you've got to break them
somewhere.
The point of 'format = flowed' and 'quoted printable' is so that modern
clients can re-assemble these lines so that they are as long as the
author originally intended. Using '72' as the break point is just a
convenience in case anyone is using an old, teletype-era news client
(is anyone??). But every newsreader in the world these days will
correctly reassemble the lines.
So you should use format=flowed or format=quoted printable. The lines
in your messages will be as long as you intended. URLs won't break in
the middle, and everyone will be happy!
But of course some people don't like reading great long lines. They
prefer them to wrap, so that they don't need to move their eyeballs so
much. That's their decision. You - as the sender of the message -
shouldn't concern yourself with this. Some people might like their
messages to wrap at '40'. Some at '72'. Others at the margin of the
text display. You can't cater for them all.
So it's up to the *reader* of the messages - not the *sender* to wrap
them if that's what they want to do. You can configure XanaNews to do
this in Tools/Options/Message Pane, 'Wrap lines at 'n' characters'."