From: Peter C. <pet...@ne...> - 2001-12-07 15:44:53
|
> From: J.P. King [mailto:jp...@he...] > *blink* So do you think that our website should check the client > connecting, and if it is lynx then it should automatically filter all > images through a gif->ascii-art translator, in order to cope with > the lowest common denominator? Hey, cool idea! Instant ASCII art! > If it was a question of the mud not being _usable_ by a client > then this would be an issue, but default telnet is good enough > to use it just isn't great. At least MS telnet is *not* good enough to use --- and that's the one that many of our new users would be using if attracted via a telnet: URL on the Web site. In particular, there's one character sequence (Ctl-S) that renders the connection unusable. If there's a way of reducing the impact of this --- I do it fairly regularly when aiming for Shift-S and missing --- then I think we should implement it. But, no, I'm not arguing for full connection and terminal management. That's a job for the client. [My own opinion is that @recall is also a job for the client, but that doesn't appear to have prevented its implementation. Ditto colour. Opinions vary.] - Peter |