Don’t worry, I’m sure both remaining users of Gopher won’t mind.
:-D
- Kim
If any of you are on the #gopherproject IRC channel, you may have noticed a new presence there. Today I enabled IRC chat integration into the game's already made chat system. So now players of the game can seamlessly chat about gopher with people in the #gopherproject IRC channel. Now you can seamlessly chat gopher while beta testing. I will soon add gopher mailing list integration so that you can read through and reply back to messages on this list.
The gopher community is going to have a presence in this game whether they like it or not. I'm honestly not sure if I should put a "just kidding" after this bold statement or not... all I know is that after writing it, I couldn't stop laughing. On February 14, 2015 6:13:41 PM MST, Kevin Veroneau < kevin@veroneau.net> wrote:
I had a beta tester online last night, and we were able to really test out the
chat system, and it seems to work near flawless. He also runs on Windows, and
found that the web-based terminal had some interesting limits. I was looking
into replacing this web client and using a full VT100 Terminal Emulator for a
little while now. I finally updated the web client today and released it onto
the server. :)
I used the VT100 Terminal Emulator from the awesome ShellInABox project, but
the connection to the actual server is custom. It goes through WebSockets of
course, rather than AJAX. I did some basic tests of the VT100 client code,
and so far it works almost the same as you would expect a UNIX Terminal
Emulator to function.
Nobody has redeemed any of the previous codes yet, so they are still up for
grabs.
On February 12, 2015 08:31:27 AM Kevin Veroneau wrote:
I actually tried Putty last night and it doesn't follow RFC making it not
work sadly. I am working on a vt100 emulator made in SDL, so it will be
fully cross platform, and even support game specific features. This
client will also be able to play .MOD files as you play the game. Not
sure why so many telnet clients out there don't follow RFC, and base their
settings solely on how the UNIX telnetd works. I can't maintain a server
that supports every single type of client quirk.
On February 12, 2015 1:35:04 AM MST, Nuno Silva <nunojsilva@ist.utl.pt>
wrote:
On 2015-02-11 12:25, Wolfgang Faust wrote:
On Feb 11, 2015 10:34 AM, "Kevin Veroneau" <kevin@veroneau.net>
wrote:
I also recently found out that the Windows telnet client(at least
on XP)
doesn't work very well.
And Windows 7 doesn't come with a Telnet client at all--you have to
know
the magic incantation to install it afterwards. If you haven't
already, you
may want to consider implementing a web-based client. There are flash
and
java-based ones that you can just plug your hostname into, or you
could set
up a Websocket server and have a pure _javascript_ one.
(Personally, I use TinyFugue. I won't be redeeming a beta code
because I'm
very busy this week, so I'll leave them for someone else.)
What about putty? I can try to have a look at it, if I have time. I use
it mostly for SSH from windows boxen, but why not try it with telnet.
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
--
Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.orghttp://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
|