Nuts IV
Andy Fiddaman
been a while!
It must be the year for it as I restarted development of the JeamLand talker
code in October and am just about ready to release version 1.4 (a couple of
test sites have the beta version already up and running).
I know that JeamLand is not as widely used as other talker code bases, but
I'm hoping that this new version will be more accessible, particularly to
EW2 users.
One of the things I've been working with an EW2 talker administrator who is
switching to JeamLand is to implement all common EW2 commands using the
JeamLand internal language or as JeamLand Loadable Modules. There is even a
loadable module which implements the EW2 intercom protocol so that it can
communicate with other talkers. These enhancements will be released
separately after the main talker code.
To quote Neil, watch this space....
A.
ne...@ogham.demon.co.uk
>Neil - Glad to hear you're back in the talker development business, it's
>been a while!
Indeed it has. And this will probably be my last big freeware project as
I'm getting tired of programming these days , but I had an idea for NUTS 4
in mind and wanted to develop it before (if)I jack in the coding altogether :)
>It must be the year for it as I restarted development of the JeamLand talker
>code in October and am just about ready to release version 1.4 (a couple of
>test sites have the beta version already up and running).
Post the addresses!
>JeamLand internal language or as JeamLand Loadable Modules. There is even a
>loadable module which implements the EW2 intercom protocol so that it can
>communicate with other talkers. These enhancements will be released
>separately after the main talker code.
The protocol I've put in nuts 4 allows people to traverse servers across
the net (almost) transparently hopping from one to he next (unlike in nuts 3
where you could only hop one stop) as well as emails, remote tells etc etc.
Perhaps when nuts 4 is done you might want to put it in Jeamland? I don't
have any docs on it yet though as all my time is taken up with the code :)
NJR
Winzlo
> >code in October and am just about ready to release version 1.4 (a couple of
> >test sites have the beta version already up and running).
>
> Post the addresses!
I'm running Jeamland 1.4.0 (beta) on my-harmonix.com 5000, which is
also the first Mac OS X port of Jeamland. Orchard is still there too,
at orchard.jeamland.org 4141.
> >JeamLand internal language or as JeamLand Loadable Modules. There is even a
> >loadable module which implements the EW2 intercom protocol so that it can
> >communicate with other talkers. These enhancements will be released
> >separately after the main talker code.
>
> The protocol I've put in nuts 4 allows people to traverse servers across
> the net (almost) transparently hopping from one to he next (unlike in nuts 3
> where you could only hop one stop) as well as emails, remote tells etc etc.
> Perhaps when nuts 4 is done you might want to put it in Jeamland? I don't
> have any docs on it yet though as all my time is taken up with the code :)
Jeamland has done a heck of a job in unifying protocols and providing
command compatibility, to make the code most friendly, and capable of
communicating with the other major communication systems. Once you
have things finished, I'd love to see that kind of technology in
Jeamland (I think Alcides would have me rubbed out if I proposed it
for 1.4 <Smirk>)
It's high time that the EW2, NUTS and IRC communities unite, in one
giant effort to better consolidate users and re-kindle the talker
experience for everyone (especially those of us that miss good old
fashioned chatting, versus meaningless babble.)
Neil
> It's high time that the EW2, NUTS and IRC communities unite, in one
> giant effort to better consolidate users and re-kindle the talker
> experience for everyone (especially those of us that miss good old
> fashioned chatting, versus meaningless babble.)
Not sure how many users are left to consolidate now that most of the
interest is focused on instant messaging and web based chatrooms.
Anyway , nuts 4 now works properly with windows (still broken) telnet
implementation so hopefully I might be able to persuade new people to
use it.
NJR
Tarsi
> interest is focused on instant messaging and web based chatrooms.
On the place I code/run (foreverbeyond.org 7000), we've had several AOL
AIM users come by who were at first VERY intimidated, but stuck with it,
and now prefer it over AIM for chatting. They find it a more warm,
personable, social environment, and the extra commmands and functions
are better than just the plain chat of AIM. The lack of gfx doesn't
seem to bother them, they just get more creative in their speech --
which we all love to see.
I think it's still a valid field to pursue, although I'd admit that the
audience has shrunk and the ability (or patience) of the users is
getting lower.
On a similar related note, anyone ever thought of coding an
AIM/ICQ/Yahoo/MSN gateway into their talker?
> Anyway , nuts 4 now works properly with windows (still broken) telnet
> implementation so hopefully I might be able to persuade new people to
> use it.
I'd be curious, Neil, to hear about this....if you went and put code in
that detected the (broken) Windows telnet and did special things, or
just always compensated for the brokenness(?).
Tarsi
Andy Fiddaman
> that detected the (broken) Windows telnet and did special things, or
> just always compensated for the brokenness(?).
Me too Neil ;)
I haven't done much with this in JeamLand yet, but the two problems I'm
aware of are that the client refuses to allow the talker to turn echo on and
off (at least using the standard IAC messages) and it sends line feed
characters which are a little odd although they can be handled (or you can
just force the talker to print extra newlines at the
end of commands).
A.
ne...@ogham.demon.co.uk
Those may well be problems with windows telnet too (I've not had any problems
with echo I have to say), but for me its main problem is that it specifically
breaks RFC854. I quote:
TRANSMISSION OF DATA
Although a TELNET connection through the network is intrinsically
full duplex, the NVT is to be viewed as a half-duplex device
operating in a line-buffered mode. That is, unless and until
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Postel & Reynolds [Page 4]
RFC 854 May 1983
options are negotiated to the contrary, the following default
conditions pertain to the transmission of data over the TELNET
connection:
1) Insofar as the availability of local buffer space permits,
data should be accumulated in the host where it is generated
until a complete line of data is ready for transmission, or
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
etc....
Ie ALL programs acting as telnet clients (and servers for that matter) should
default to line mode unless otherwise requested or buffer space is low.
No version of windows telnet has ever done this AFAIK (and I've tried it on
win 3.1 , 95, 98 , NT4 , 2000) they all default to character mode (unlike unix
telnets which default to line mode and hence work fine with all talkers, mud
servers etc). Its another example of MS picking and choosing which bit of an
RFC it will adhere to. Anyway , to solve this problem NUTS 4 receives input in
character mode (and because I've used facility for something it won't work
with a line mode only client).
NJR