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 BA243D682; Tue, 11 Aug 2020 21:54:55 +0000 (UTC) Received: from [127.0.0.1] (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 894E4D616; Tue, 11 Aug 2020 21:54:49 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 496) id 99113D55E; Tue, 11 Aug 2020 21:54:47 +0000 (UTC) Received: from mail.xndr.de (mail.xndr.de [176.9.45.248]) by atuin.qyliss.net (Postfix) with ESMTPS id 1B327D55C for ; Tue, 11 Aug 2020 21:54:44 +0000 (UTC) References: <874kp99m8v.fsf@xndr.de> <877du5owz2.fsf@alyssa.is> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xndr.de; s=mail; t=1597182881; bh=UdaAvqj69T+A8c7aQUjFhNOycJJ52f7T/magPZfu4yk=; h=References:From:To:Cc:Subject:In-reply-to:Date; b=IQmU71QSomIVRLmk1pnIF08rMMhHg+dhU+21qrXYm/6sW0VtbFX/OoKCZR/d2B/AH CsiOURJxhaivWQXBycDWQVsPQDJdppNkIGHKIZm73dNh5BJwk7e5jhykq7eBMESzMp GiIaYyaU1jZjKr4dq3ocXFqAh1IBeA4PP4J+nBl8= From: Philipp =?utf-8?Q?Steinpa=C3=9F?= To: Alyssa Ross Subject: Re: [PATCH] Add and clarify matrix workarounds. In-reply-to: <877du5owz2.fsf@alyssa.is> Date: Tue, 11 Aug 2020 23:54:38 +0200 Message-ID: <871rkcalwh.fsf@xndr.de> MIME-Version: 1.0 Content-Type: text/plain Message-ID-Hash: F6ATCTV2D76UKBKAP226IPWH2J34JQVR X-Message-ID-Hash: F6ATCTV2D76UKBKAP226IPWH2J34JQVR X-MailFrom: philipp@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 CC: Philipp , devel@spectrum-os.org 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: Thank you for the remarks, they were all very helpfull. If you want to include me in the copyright, you are free to use my full name. It's in the mail header now. P.S. Please feel free to comment on any potential problems with the formatting of these patch mails, if you want to. It's my first time using git via mail and I'd like todo it the proper way right away. --- participating.html | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/participating.html b/participating.html index 811fcf4..10665ca 100644 --- a/participating.html +++ b/participating.html @@ -78,13 +78,18 @@ 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: - -

    -
  1. Post !join #spectrum in your "Freenode IRC Bridge" chat.
    2. -
  2. Accept the invitation you are sent.
    3. -
+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. +

If you experience this issue, kindly report it to the people who run -- 2.28.0 Alyssa Ross writes: > Philipp writes: > >> 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(-) > > Thanks for the patch! This should be very helpful. I have a couple of > comments, but I'm happy to just fix them up myself if you prefer. > >> 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: > > Text should be wrapped as it is everywhere else (I wrap at 70 because > it's the default in Emacs but it doesn't have to be exact). > > The room name also isn't really a quotation, so probably doesn't really > make sense to be a . (I think I'd just not mark it up at all.) > >> + >> +

    >> +
  • 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.
    • > > The messages probably make more sense as than . > The can also be omitted. > >> +
>> >> -
    >> -
  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 > > As I said above, I'm happy to just fix up the patch myself and apply it if > you'd prefer. > > One more thing -- this probably makes you a (minor) copyright holder in > this file. Are you happy if I add "SPDX-FileCopyrightText: 2020 > Philipp" to the copyright header at the top of the file? (You can give > me a surname if you want, or not -- up to you.) And would you prefer > your email address be included in the notice, or not (either is fine)?