@rook said in Alternative Formats to MU:
But at face value, it is just text being sent back and forth. The channel in which it is process doesn't matter to the end-user.
The point is that it doesn't have to be just text being sent back and forth.
Evennia's model is that you have a Portal (which accepts incoming connections, be they telnet, ssh, or the web client) and a Server (which does all the actual work). All the text sent from the Server to the Portal can support out-of-band metadata. For telnet/ssh, this metadata is just stripped off, but why not do things like show a typing indicator in the web client?
You could also do things like make a map in the web client that supports receiving your current location from the server and putting a little pin on the graphical map showing 'you are here'. You could send a list of people in the room as people enter and exit. You could include things like 'this blob of text is a page associated with conversation 1' and make the web client pop the page conversation out into its own window, a'la instant messenger.
A list of people presently online on the game, where you can click on one and have it open a private messaging conversation to them, is arguably a lot more intuitive to everyone who uses the internet than knowing you need to 'page <blah>=<foo>'. Everyone's used to being able to do that on Discord servers already, or Battle.net, or Steam, or Skype, or IRC, or whatever.
And that's without getting into a complete rewrite from scratch where Telnet isn't even part of it, and the web client isn't just some 'richer' way to access it that can use extra metadata.