An implementation of the RFC1288 protocol, written in Go. #complete
Go to file
Elf M. Sternberg 73b0f90c16 COMPLETE: A relatively straightforward implementation of the Monologued server.
This is obviously a version 1.0, but it taught me a few things about Go's
networking and its batteries included philosophy.  I'll have a longer blog
post about it in a few days.  It still needs a configuration file and a
couple of other features found in traditional finger servers, but for now
this is a pretty good example.
2018-01-10 14:27:33 -08:00
dotplan COMPLETE: A relatively straightforward implementation of the Monologued server. 2018-01-10 14:27:33 -08:00
rfc1288 COMPLETE: A relatively straightforward implementation of the Monologued server. 2018-01-10 14:27:33 -08:00
.gitignore Initial commit -- RFC1288 parser is passing unit tests. 2018-01-09 15:41:51 -08:00
LICENSE Initial commit 2018-01-09 14:36:26 -08:00
README.md Initial commit -- RFC1288 parser is passing unit tests. 2018-01-09 15:41:51 -08:00
main.go COMPLETE: A relatively straightforward implementation of the Monologued server. 2018-01-10 14:27:33 -08:00

README.md

MONOLOGUED

Monologued is an implementation of an RFC1288 protocol server in Go.

That's right. Monologued is a Finger server.

WHY‽‽‽‽

While what I really wanted was to learn Rust, work decided that Go was a better choice. Since I have to learn it, this seemed like the best way to go about it. Still not thrilled with the decision, but maybe I'll get a blog post out of it.

Status

Monologued is still very much not working. Don't even bother downloading. It's mostly something to cut my teeth on while I try to figure out how Go works.

Thanks

Thanks to my friend Nathaniel for the answer to my original question, "In a movie, when the villain is explaining his plans at length, what is that called?" Nathaniel explained that "He's monologuing," and now you know why it has that name.

License

Apache 2.0. See the accompanying LICENSE file in this directory.