[meta] Issues to be resolved to enable Matrix bridging with IRC

Identity/Impersonation protection

• Minimum: Bridged protocols should check for a registered nick via services, and prompt users to authenticate and/or register the new nick.
• Preferred: Bridged protocols should use a central authentication authority such as an Oauth endpoint of Drupal.org (which does not yet exist). As well as checking for the nick being registered before the bridged connection is created.

Notification

• Bridged rooms should notify users of what other protocols the channel is bridged to (notification must appear to users on all sides of the bridge)
• Bridged rooms should notify users that some bridged protocols won't support edited or deleted comments.
• Kick/ban notices need to propagate properly across bridges.
• Ghosting and presence indicators must propagate properly across bridges.

Moderation

• The team of moderators should be equal across bridged platforms, with equal privileges on all sides of a bridge.
• Moderators for any protocols involved in the bridge must apply in the issue queue and be approved by the current team of moderators.
• The bridge needs to allow moderators to disable or enable the bridge from either side.

Configuration management

• The proper setup and configuration of a) a matrix server b) channel bridging c) etc need to be well documented so they can be understood by the DA infrastructure team.
• A puppet manifest for managing that server should be generated.