MRC Chat platform

Intro

The Multi Relay Chat platform is undergoing a major transformation. Thanks to Gryphon for the initial version.

This transformation will happen in multiple stages and feedback is always appreciated.

Developers

If you are a developer and would like to port MRC to your platform, please follow the following process to get access to the protocol documentation.

1. Create an account on the Wiki
2. Send StackFault a BBS e-mail on The Bottomless Abyss, a netmail or Internet email to: sysop (at) bottomlessabyss (dot) net)

Once your request have been approved, you will have access to the MRC development namespace here:

MRCDoc:MRC Protocol

Stage 1

Many issues existed in the client portion of MRC. These issues have been resolved with the release of an updated client replacing the MPL script.

Backward compatibility with v1.1 is maintained allowing a mix of older and newer clients to interact while a transition is worked out.

Quick adoption of this release have seen many BBSes adopt the new client.

Stage 2

The server was moved to a DC hosted server to ensure better availability and allow for some minor performance improvement.

A new server codebase is being developed from scratch to address many of the issues identified previously while maintaining backward compatibility with the v1.1 implementation.

Stage 3

Cross-platform interoperability documentation is being developed to allow the platform to extend beyond the Mystic BBS base.

This will allow other platforms to interact easily with the platform, creating a uniform chat experience.

If you are a developer and wish to create a client for a platform not listed below, please reach out to StackFault and ask for access to the development team.

List of platforms currently interested

• Mystic
• CNet
• WildCat
• Synchronet

Stage 4

Deployment of the new server have been completed on March 5th 2019.

The release of a new MRC package containing the Mystic UI and Mystic client was made at the same date.

This release is now called Multi Relay Chat and shows v1.2.5.

Many new options are included in the release, including:

New Server code includes the following improvements

• Multi-threaded architecture
• Message queuing
• Improved validation of connections
• Improved keep-alive mechanisms
• Faster roundtrip of messages
• Increased connection capacity
• BBS information screens
• Better announcement of connecting users
• New server commands
• Many more smaller improvements

New Mystic UI improvements

• Handle auto-completion
• Better support for customization
• Many more smaller improvements

New Mystic client improvements

• Auto-reconnect within the client
• Support for the new server commands
• Improved keep-alive mechanism
• Support for server-side managed rooms
• Many more smaller improvements

Screenshot of current 1.2.6-dev

New from 1.2.5:

• Latency reporting
• New STATS server command (available via /QUOTE)
• New TIME server command (available via /QUOTE)
• Many small issues and optimizations
• Welcome message when entering room with number of users
• Removed the server generated "joined room" message for self

Feedback

Feedback is appreciated, please report any issues found to StackFault, either in MRC directly, by logging in to The Bottomless Abyss or via netmail.

Brainstorming

Here we can list ideas for future features for MRC.

• Vote on a user being muted.
• /whois <username> command - The whois command would allow a user to set one line of text about themselves. ie: Stackfault - SysOp of Bottomless Abyss BBS Member of: Phenom.
• Loyalty points: If a particular user helps another user of the chat, that user can +1 the helping user. And would be issued 1 (one) help point. This information would be displayed with the /whois command.
• Offline messaging
  • If you send an offline message to a user, Your private message will be sent and when that user logs on again, the message(s) would be delivered.

• Global Channels
  • Global channels would be used for group conversations.
    • When initially logging on to MRC every user is put on a default 'Sub-Channel' example: channel 1234.
    • To change global channels =t <channel number> (1-65535)
    • To send a message on that global channel prefix all messages with '
    • All sub channel messages could be listed in a different color (Bright yellow?)
    • To display who is currently on your global channel press ' all by itself.