Hacker News Reader

Comment by beaugunderson | Hacker News Reader

Some of my first programming experience was using the language inside of a MUSH (TinyTIM to be specific, based on TinyMUSH but heavily modified). Interactive experiences could be built up using the rudimentary logic afforded.

Found this repository of MUSH code if anyone is curious what it looked like: https://www.mushcode.com/

Modifying Eggdrop (the IRC bot written in C) was another project that contributed to my early understanding.

View on HN

tim.org is still online. Originally started by Jason Scott of textfiles.com and now at archive.org.

I'm convinced the Slack-killer is going to be a user programmable MUSH.

That's what Slack kind of started out as right? (it was a multiplayer game)

Slack was born out of the (second) attempt by Butterfield to build a game. But Slack didn't start out as a game; there was a game being built, and it didn't evolve into Slack—they productized their internal comms (a separate thing that they built and were using in the course of making the game).

MOOs have been around forever and are like more-easily programmable MUSHes. Educational institutions loved them back in the day. There's even still development of the MOO server, active social MOOs, websites running MOO as the webserver... lots of fun stuff!

If there's any interest:

Archived MOO knowledge: https://lisdude.com/moo/ Modern MOO server: https://github.com/lisdude/toaststunt/ Active social MOO: https://chatmud.com/

Reply on news.ycombinator.com