Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
matrix [2020/08/10 09:03]
rubin [What is it?] 		matrix [2021/06/09 10:16]
voice [Room and Account Names]
Line 35: Line 35:
   * Matrix rooms utilize the following format, also called an alias: #roomname:homeserver.tld A room must have this set in order to be public, otherwise it is assumed to be private and invite only.   * Matrix rooms utilize the following format, also called an alias: #roomname:homeserver.tld A room must have this set in order to be public, otherwise it is assumed to be private and invite only.
   * Matrix accounts utilize the following format: @account:homeserver.tld   * Matrix accounts utilize the following format: @account:homeserver.tld
-  * AfterNET IRC bridged rooms utilize the following format: #irc_#channel:afternet.org+  * AfterNET IRC bridged rooms utilize the following format: #channel:afternet.org
   * Other bridged networks and their room formats are available [[https://github.com/matrix-org/matrix-appservice-irc/wiki/Bridged-IRC-networks|here.]]   * Other bridged networks and their room formats are available [[https://github.com/matrix-org/matrix-appservice-irc/wiki/Bridged-IRC-networks|here.]]
  
Line 117: Line 117:
   * The IRC bridges are managed by the homeserver operator they are attached to, ie: AfterNET manages the bridge to the AfterNET IRC network and matrix.org manages the bridge to the Freenode IRC network.   * The IRC bridges are managed by the homeserver operator they are attached to, ie: AfterNET manages the bridge to the AfterNET IRC network and matrix.org manages the bridge to the Freenode IRC network.
   * Nothing is perfect and this is no different. The bridge may from time to time exhibit odd behaviors such as communication going only one way, that is to say a user may send a message to a bridge room from the Matrix side but it wont make it to the IRC side or vice versa. This is a known issue with the bridging software.   * Nothing is perfect and this is no different. The bridge may from time to time exhibit odd behaviors such as communication going only one way, that is to say a user may send a message to a bridge room from the Matrix side but it wont make it to the IRC side or vice versa. This is a known issue with the bridging software.
-  * **Lag exists.** Due to the way the homeserver and bridge service communicate it can take a little time for messages to process, it has been observed that this can take up to five minutes. This is likely due to a limitation in both the homeserver and the bridge software.+  * **Lag exists.** Due to the way the homeserver and bridge service communicate it can take a little time for messages to process, it has been observed that this can take up to five minutes. This is likely due to a limitation in both the homeserver and the bridge software. //This is becoming less of an issue.//
  
 ==== @appservice-irc:afternet.org ==== ==== @appservice-irc:afternet.org ====
Line 127: Line 127:
  
 ==== Bridge Rooms ==== ==== Bridge Rooms ====
-As stated earlier, the name format for bridged rooms on AfterNET IRC is #irc_#channel:afternet.org. So for example #linux on AfterNET IRC goes by #irc_#linux:afternet.org on the AfterNET homeserver.+As stated earlier, the name format for bridged rooms on AfterNET IRC is #channel:afternet.org. So for example #linux on AfterNET IRC goes by #linux:afternet.org on the AfterNET homeserver.
  
-Rooms not listed in the Room Explorer can be joined by doing /join #irc_#channel:afternet.org in your Matrix client. +Rooms not listed in the Room Explorer can be joined by doing /join #channel:afternet.org in your Matrix client. 

Page Tools