 |
KGSueMe - Default branch
|
Section: Unix
|
|
|
|
| Added: Mon, Jun 2nd 2003 07:22 PDT (4 years, 11 months ago) |
Updated: Thu, May 1st 2008 00:07 PDT (20 days ago) |
|
|
About:
KGSSueMe aims to provide a sample implementation
of a client for the popular Kiseido Go Server.
The project stresses documenting the protocol by
giving developers code, so that they can write
their own clients, rather than to provide a
featureful client.
Author:
Marc A. Lehmann [contact developer]
Homepage:
http://software.schmorp.de/#kgsueme
CVS tree (cvsweb):
http://cvs.schmorp.de/kgsueme/
Trove categories:
[change]
Dependencies:
[change]
No dependencies filed
|
|
» Rating:
(not rated)
» Vitality: 0.00% (Rank 19538)
» Popularity: 0.29% (Rank 18595)
 
(click to enlarge graphs)
Record hits: 4,298
URL hits: 844
Subscribers: 5
|
|
Branches
Comments
[»]
Why conflict?
by Ilya Martynov - Sep 21st 2003 02:01:30
From the name of the project and comments in documentation it seem William
Shubert is not willing to disclose KGS protocol. I'm curious - why?
--
Ilya Martynov (http://martynov.org/)
[reply]
[top]
[»]
Re: Why conflict?
by Marc Lehmann - Jan 17th 2004 08:39:25
> From the name of the project and
> comments in documentation it seem
> William Shubert is not willing to
> disclose KGS protocol. I'm curious -
> why?
True. The reports on the reasons are conflicting. On various occasions he
publicly said he will disclose the source code under the GPL at a later
time, or that he would open up the source if he was allowed to by the
contract he has, but he mustn't.
However, he also said publicly that he would be very pissed off if anybody
else would write another client or would reverse-engineer the protocol, and
this is why he keeps the source (and the protocol, which are two different
things of course) seperate.
In private mail he even told me that he will change the protocol just to
keep me out, and he did this once, adding "encryption" (kind of bit games)
to the protocol without adding any new functionality (or any other need to
change). Obviously, keeping the protocol secret is important enough for
him to force all users to upgrade their software. His argument is that if
there were other clients available that would make it impossible to
enhance the software.
Go figure, I have no idea what drives him, especially since version one of
his client (v1 works only with standard igs/nngs-type servers, v2 only
works with his own server) was GPL'ed. Maybe it didn't work for him, but
to my knowledge, he never said anything more specific about his reasons
even when asked.
[reply]
[top]
[»]
Re: Why conflict?
by Linux Dancer - Apr 27th 2006 10:08:27
Just found this, does it still work with CGoban 2.12?
[reply]
[top]
|
|
|
