From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.3 (2019-12-06) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.3 Received: by atuin.qyliss.net (Postfix, from userid 496) id 73321D389; Tue, 11 Aug 2020 16:32:43 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id BD55ED33D; Tue, 11 Aug 2020 16:32:35 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id DF153D332; Tue, 11 Aug 2020 16:32:34 +0000 (UTC) Received: from mail.xndr.de (mail.xndr.de [176.9.45.248]) by atuin.qyliss.net (Postfix) with ESMTPS id C2972D338 for ; Tue, 11 Aug 2020 16:32:32 +0000 (UTC) From: Philipp DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xndr.de; s=mail; t=1597163552; bh=c/7VBHAmmPBa8i9zlWvMZi0s2/9QtSLUK6AS3959W30=; h=From:To:Subject:Date; b=ODjVHfAQYP+Wv7hX0VSB2SVCCp2mALUex90cBs4yvz8/Ru33paXfeC1v45Ewzirjt IOLYjpmUSVUoqidqJinR69ciYuHp1lx2XKKMjMKwHsik3qyITTeYT3c7jfCH+H90Fy CjOb0IDCIzWt7EQouQ0embuhkGm6tI5OzW6C2+Sg= To: devel@spectrum-os.org Subject: [PATCH] Add and clarify matrix workarounds. Date: Tue, 11 Aug 2020 18:32:32 +0200 Message-ID: <874kp99m8v.fsf@xndr.de> MIME-Version: 1.0 Content-Type: text/plain Message-ID-Hash: 6XZCJQ33LREODJK33JIAPGW6CCPGRW75 X-Message-ID-Hash: 6XZCJQ33LREODJK33JIAPGW6CCPGRW75 X-MailFrom: philipp+spectrum@xndr.de X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.1 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: I'm a matrix user and fiddled around with the room there a bit. My findings were that the room itself seems to be fine, but the pretty alias is broken in some way that I don't understand. I came up with two ways to join the room via the internal ID and I also took the liberty to modify the old workaround a little and made it more precise. --- participating.html | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/participating.html b/participating.html index 811fcf4..58f2ff3 100644 --- a/participating.html +++ b/participating.html @@ -78,13 +78,15 @@ the web.

Note for Matrix users

-There appears to be an issue with Matrix's IRC bridge that prevents -Matrix users from joining #spectrum. The workaround is as follows: +There appears to be an issue with Matrix's IRC bridged room that prevents +Matrix users from joining the channel with the normal alias #freenode_#spectrum:matrix.org. There are the following workarounds: + +

    +
  • Join the room via it's internal name: /join !ZsIiqZmCTSWHpTQWaw:matrix.org. +
  • Join the room via matrix.to link.
    • +
  • Ask the bridges appservice to invite you to the room: /msg @appservice-irc:matrix.org !join #spectrum and accept the invite.
    • +
-
    -
  1. Post !join #spectrum in your "Freenode IRC Bridge" chat.
    2. -
  2. Accept the invitation you are sent.
    3. -

If you experience this issue, kindly report it to the people who run -- 2.28.0