deploy: 0455c40

develop/.sample_config_header.yaml

@@ -1,12 +1,11 @@
 # This file is maintained as an up-to-date snapshot of the default
 # homeserver.yaml configuration generated by Synapse. You can find a
 # complete accounting of possible configuration options at
-# https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html
+# https://element-hq.github.io/synapse/latest/usage/configuration/config_documentation.html
 #
 # It is *not* intended to be copied and used as the basis for a real
 # homeserver.yaml. Instead, if you are starting from scratch, please generate
 # a fresh config using Synapse by following the instructions in
-# https://matrix-org.github.io/synapse/latest/setup/installation.html.
+# https://element-hq.github.io/synapse/latest/setup/installation.html.
 #
 ################################################################################
-

develop/admin_api/README.rst

@@ -1,7 +1,7 @@
 Admin APIs
 ==========
 
-**Note**: The latest documentation can be viewed `here <https://matrix-org.github.io/synapse>`_.
+**Note**: The latest documentation can be viewed `here <https://element-hq.github.io/synapse>`_.
 See `docs/README.md <../README.md>`_ for more information.
 
 **Please update links to point to the website instead.** Existing files in this directory
@@ -11,4 +11,3 @@ This directory includes documentation for the various synapse specific admin
 APIs available. Updates to the existing Admin API documentation should still
 be made to these files, but any new documentation files should instead be placed under
 `docs/usage/administration/admin_api <../usage/administration/admin_api>`_.
-

develop/development/demo.html

@@ -161,7 +161,7 @@ <h1 class="menu-title">Synapse</h1>
 
                         <h1 id="synapse-demo-setup"><a class="header" href="#synapse-demo-setup">Synapse demo setup</a></h1>
 <p><strong>DO NOT USE THESE DEMO SERVERS IN PRODUCTION</strong></p>
-<p>Requires you to have a <a href="https://matrix-org.github.io/synapse/develop/development/contributing_guide.html#4-install-the-dependencies">Synapse development environment setup</a>.</p>
+<p>Requires you to have a <a href="https://element-hq.github.io/synapse/develop/development/contributing_guide.html#4-install-the-dependencies">Synapse development environment setup</a>.</p>
 <p>The demo setup allows running three federation Synapse servers, with server
 names <code>localhost:8480</code>, <code>localhost:8481</code>, and <code>localhost:8482</code>.</p>
 <p>You can access them via any Matrix client over HTTP at <code>localhost:8080</code>,

develop/federate.html

@@ -203,15 +203,15 @@ <h3 id="known-issues"><a class="header" href="#known-issues">Known issues</a></h
 federating servers, which can cause <code>M_UNKNOWN</code> or <code>401 Unauthorized</code> errors. This
 may affect users who are redirecting apex-to-www (e.g. <code>example.com</code> -&gt; <code>www.example.com</code>),
 and especially users of the Kubernetes <em>Nginx Ingress</em> module, which uses 308 redirect
-codes by default. For those Kubernetes users, <a href="https://stackoverflow.com/a/52617528/5096871">this Stackoverflow post</a> 
+codes by default. For those Kubernetes users, <a href="https://stackoverflow.com/a/52617528/5096871">this Stackoverflow post</a>
 might be helpful. For other users, switching to a <code>301 Moved Permanently</code> code may be
 an option. 308 redirect codes will be supported properly in a future
 release of Synapse.</p>
 <h2 id="running-a-demo-federation-of-synapses"><a class="header" href="#running-a-demo-federation-of-synapses">Running a demo federation of Synapses</a></h2>
 <p>If you want to get up and running quickly with a trio of homeservers in a
 private federation, there is a script in the <code>demo</code> directory. This is mainly
 useful just for development purposes. See
-<a href="https://matrix-org.github.io/synapse/develop/development/demo.html">demo scripts</a>.</p>
+<a href="https://element-hq.github.io/synapse/develop/development/demo.html">demo scripts</a>.</p>
 
                     </main>
 

develop/modules/third_party_rules_callbacks.html

@@ -322,7 +322,7 @@ <h3 id="on_profile_update"><a class="header" href="#on_profile_update"><code>on_
 per-room profiles globally using the <code>allow_per_room_profiles</code> configuration setting in
 Synapse's configuration file.
 This callback is not called when registering a user, even when setting it through the
-<a href="https://matrix-org.github.io/synapse/latest/modules/password_auth_provider_callbacks.html#get_displayname_for_registration"><code>get_displayname_for_registration</code></a>
+<a href="https://element-hq.github.io/synapse/latest/modules/password_auth_provider_callbacks.html#get_displayname_for_registration"><code>get_displayname_for_registration</code></a>
 module callback.</p>
 <p>If multiple modules implement this callback, Synapse runs them all in order.</p>
 <h3 id="on_user_deactivation_status_changed"><a class="header" href="#on_user_deactivation_status_changed"><code>on_user_deactivation_status_changed</code></a></h3>

develop/modules/writing_a_module.html

@@ -219,7 +219,7 @@ <h2 id="registering-a-callback"><a class="header" href="#registering-a-callback"
 the callback name as the argument name and the function as its value. A
 <code>register_[...]_callbacks</code> method exists for each category.</p>
 <p>Callbacks for each category can be found on their respective page of the
-<a href="https://matrix-org.github.io/synapse">Synapse documentation website</a>.</p>
+<a href="https://element-hq.github.io/synapse">Synapse documentation website</a>.</p>
 <h2 id="caching"><a class="header" href="#caching">Caching</a></h2>
 <p><em>Added in Synapse 1.74.0.</em></p>
 <p>Modules can leverage Synapse's caching tools to manage their own cached functions. This