Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

Limitations on Matrix to IRC bridging

This document gives information about what to expect when Ubuntu starts bridging existing IRC channels to Matrix rooms.

Bridging events from IRC to Matrix

There are no limitations bridging messages from IRC to Matrix.
All features are supported and translated to Matrix events.

The following Matrix to IRC events are not available or limited

  • Redaction: Redacting messages on Matrix has no effect on the IRC side.
    The message just stays as written.

  • HTML / Markdown: Some markdown language is supported. For example you can use bold text. If a markdown feature is not supported like code blocks the message is usually transmitted as plaintext.

  • Media Sharing: Matrix supports the sharing of images, videos, and files directly in chats. IRC does not inherently support media sharing. Files must be shared via URLs. Any direct media shared on Matrix will typically be converted to a URL when viewed on IRC.

  • Reply Threads: Matrix supports threaded conversations, allowing users to reply to specific messages creating a thread. IRC does not support threads in the same way, so threaded messages from Matrix will appear as standard messages on IRC, potentially losing context.

  • Reactions and Emojis: While both Matrix and IRC support the use of emojis in messages, Matrix also supports message reactions (emoji reactions to messages). These reactions do not have a direct equivalent in IRC and will not be visible.

  • Read Receipts and Typing Notifications: Matrix provides read receipts and typing notifications to indicate when users are typing a message or have read a message. IRC does not support these features, so they are not available when bridging from Matrix to IRC.

  • End-to-End Encryption: Matrix supports end-to-end encryption in rooms. IRC does not support end-to-end encryption natively; thus, encrypted messages cannot be bridged to IRC without losing encryption.

  • Room Features: Features like room topics are supported by both protocols but may not always sync perfectly across the bridge. Changes made on the Matrix side may not be reflected on IRC or may be subject to limitations based on the IRC network’s capabilities. Room avatars on Matrix are not visible on IRC.

  • Nicknames and User IDs: Matrix allows for more flexibility in usernames and displays, including spaces and special characters. IRC has stricter rules for nicknames (limited character set and length), which might result in automatic adjustments or truncation when bridging.

  • Kick/Ban Synchronization: While basic kick and ban actions can be synchronized between Matrix and IRC, the granularity of reasons, temporary bans, and more complex moderation actions may not translate perfectly across the bridge. So in general moderation has to be done on both sides.

  • Channel Modes and Permissions: IRC has a specific set of channel modes and user permissions that do not have a direct equivalent in Matrix. Bridging these settings can be challenging and may result in a loss of functionality or mismatched permissions. The map below shows the conversion of IRC user modes to Matrix power levels. This enables bridgin of IRC ops to Matrix power levels only, it does not enable the reverse. If a user has been given multiple modes, the one that maps to the highest power level will be used

    IRC mode Matrix permission level
    None 0
    Voice 1
    Operator 50 (Moderator)

This page was last modified 9 days ago. Help improve this document in the forum.