🚀 go-pugleaf

It isn't a matter of porting the bit of code - there are two different
talk protocols out there.  It would be possible to modify the talk
code to try its default protocol and, failing that, try the other,
but it would be heuristic, and not 100% reliable. It would also
lead to rather long delays in getting connected, sometimes, plus
would fail badly if the network connection was down at the time.

It makes more sense, for now, to have the two versions of talk 
available. The symptom of reaching a talk daemon of the other protocol
version is easily recognizable (as posted by the first person to ask
here) and running a different program isn't so bad.

The real problem is that talk runs as root, and you can't just port
the code and install it - the system administrators at every site would
have to evaluate its safety and then choose to install it, and then
maintain through operating system upgrades.

The best possible solution is to get the people at the remote sites
running the older version to UPGRADE.

--

Jay Vassos-Libove                  libove@alf.dec.com
Digital Equipment Corporation      decwrl!alf.dec.com!libove
Atlanta Customer Support Center    Opinions? They're mine, mine, all mine!
Alpharetta, Georgia                and D.E.C. Can't have 'em!