From 4d01764f3891004d9ff59a883ed29460fe60971f Mon Sep 17 00:00:00 2001
From: Eric Eastwood <contact@ericeastwood.com>
Date: Fri, 13 Jan 2023 18:23:19 -0600
Subject: [PATCH] Matrix bridge doesn't need to have exclusive control over the
 namespaces in a self-service world

As part of the [sunset plan for Gitter]
(https://github.com/vector-im/roadmap/issues/26), we need to make the
appservice not be exclusive over the namespaces defined in the appservice
registration file so people don't run into errors when they self-service and try to create things.

Part of https://github.com/matrix-org/matrix-hosted/issues/6979
---
 modules/matrix-bridge/lib/matrix-bridge.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/modules/matrix-bridge/lib/matrix-bridge.js b/modules/matrix-bridge/lib/matrix-bridge.js
index 9a047d7385..daf61cb60f 100644
--- a/modules/matrix-bridge/lib/matrix-bridge.js
+++ b/modules/matrix-bridge/lib/matrix-bridge.js
@@ -29,21 +29,21 @@ const registrationConfig = AppServiceRegistration.fromObject({
   namespaces: {
     users: [
       {
-        exclusive: true,
+        exclusive: false,
         // Reserve these MXID's (usernames)
         regex: `@.*-[0-9a-f]+:${serverName}`
       }
     ],
     aliases: [
       {
-        exclusive: true,
+        exclusive: false,
         // Reserve these room aliases
         regex: `#.*:${serverName}`
       }
     ],
     rooms: [
       {
-        exclusive: true,
+        exclusive: false,
         // This regex is used to define which rooms we listen to with the bridge.
         // This does not reserve the rooms like the other namespaces.
         regex: '.*'