MRC Change List on 3/3/2025:

Enhancements:

• Enhanced mention handling: user can use the /mentions command or press the UP hotkey to reset the mention counter to zero (0) and also review all previous mentions for the current session.

• User can press the PGUP hotkey as a shortcut key for /scroll

• Seconds are included in the timestamp in widescreen (132 column) mode.

• Passwords get masked when using trust commands (identify, register, roompass, update password, & roomconfig password).

Fixes:

• Added an IAMHERE immediately after connecting before joining a room. This fixes auto-joining the lobby (or the configured room) on startup. In addition, mrc-session now also passes user's terminal size, security level, IP address, and sysop's name to the MRC server on startup.

• The to_site property in messages from the server no longer needs to be considered when allowing an incoming message from mrc-connector to mrc-client. This resolves the issue of messages from ddial users not appearing in mrc-client, as well as other types of messagea (e.g.: !weather $).

• Fixed user list (nick list) refresh when someone joins a room or their client session times out.

• Stats on the status line no longer wait for user input to get updated.

• Commands not strictly defined in mrc-session are no longer stopped from being sent out to the server. This means server commands are no longer required to be issued with /quote (but it will still work for things like /quote help for the server command list).

• The HOME, END, INSERT, and PAGEDN keys no longer send an empty message if accidentally pressed.

• mrc-connector.js now announces a user's departure immediately before sending the LOGOFF command.

• Fixed an issue in mrc-client.js where the new_alias function saved the new default alias string, but didn't actually use the new alias string for the current session.

New Features:

• Basic twit filter implemented. Hides messages from problematic chatters. Usage:

  • /twit add nameoftwit Filters out nameoftwit's messages.
  • /twit del nameoftwit nameoftwit's messages are re-allowed.
  • /twit list Lists twits the user has added.
  • /twit clear Empty's the user's twit list. Twit names are saved per-user to mrc-client.ini (separated by ~ character) and remembered in future sessions.

• User can press the LEFT and RIGHT arrow hotkeys to change their outgoing message color. The selected color is indicated by the > symbol to the left of the inputline, and gets saved and reused in future sessions.

• Added "commands" option under [startup] in mrc-client.ini. This is a comma-separated list of commands defined by the sysop to execute when a user enters MRC. For example, including "chatters" will automatically display chatters in the current room on startup after displaying the motd screen and joining the room (requested by Amessyroom of Too Lazy BBS).

• Local system messages for the user get displayed in the chat window (e.g.: email notifications, new echomail posts & replies, etc.). This way the user doesn't need to wait until leaving MRC to be notified of such things.

• Added /r as a shortcut to reply to the last private message.

• User can use the CTRL+D shortcut to clear the inputline, rather than having to repeatedly press backspace.

• Optional "MRC for Synchronet" splash on startup. Sysop can customize it by editing the mrc-splash.msg file, or just disable it entirely by setting splash = false in mrc-client.ini.

Housekeeping:

• Massive reorganization of the /help information. All help info on local commands is now contained in external msg files. Redundant and obsolete commands have been removed, and text has been added to bring awareness to additional server command availability by typing /quote help

• "banners" is not a command that the server expects to receive from clients in the USER context, so the banners definition in mrc-session.js, the associated function call in mrc-client.js, and the associated setting in mrc-session.ini have been removed.

• Updated readme.txt file, including info on the toggle_nicks setting that was missed in the previous update.

Known issue:

• Strings starting with semicolons do not go out, because they are recognized by InputLine.js as sysop command prefixes. Maybe the "submit" command can be overridden to bypass this.

Acknowledgements:

Big thanks to StingRay, cr1mson, paulie420, and MeaTLoTioN for testing and providing helpful feedback, and as always to StackFault for insight.