On 2004-03-19, B a r r y penned:
Quoted message said:bomba said:Why do you assume text-only clients are backwards?
I've used them when that's all that was available, and on
systems with little to no resources. In fact _I_ prefer
text-only over Outlook, web-based news readers, and many
of the dumbed down readers.
I use them because text interfaces allow me to avoid the
mouse as much as possible. I also like to use them because
it provides portability -- no matter where I am, I can ssh
home and view my mail, my news, etc. Everything's already
set up and the stuff I've already read is actually marked as
such. Even better, I can leave the process running on
screen, go to work, load up screen again, and see the same
edit window I had at home. Which is what I've just done.
Quoted message said:Quoted message said:And why do you need a fancy reader for reading a group
that is specifically text-only?
You don't need one at all. Readers like Agent simply add
many useful features at little to no cost, of money or
'puter resources. I apologize for the slam on text
readers, and agree it's personal preference. Nothing wrong
with personal preference.
Again, if you want to keep your own configuration on any
machine you encounter, the bandwidth resources involved in
viewing a GUI across most connections isn't really worth it
compared to the speed of a text interface.
Quoted message said:Back to the subject line.
How does Tiny Url make things easier for those using a text-
only reader? A link to TU still shows up as "<a href....",
correct?
Yes, but if the url is short enough, I don't need to copy,
paste, copy second part, paste, copy third part, paste ...
Btw, there are programs like urlview that allow you to
extract urls and view them with a gui app through your
console app. The problem is that many urls arrive truncated
(I assume the sending client is responsible) and thereby
ruin that ability.
Quoted message said:On another note, don't you agree that anyone considering
themselves geeky enough to set up and use a text-only
reader over Linux should know how to bracket a URL
according to the RFC? The brackets protect the wrap on
just about any properly set up readers.
I hope no one chooses an interface based on how "geeky" they
consider myself. I use the one that works best for me, which
often but not always is command-line or console.
Me, I didn't know about that rfc, although I have seen the
notation. It's now duly noted =)
--
monique