From: dan <dandenson@gmail.com>
To: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
Cc: "LibreQoS@lists.bufferbloat.net" <LibreQoS@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Mailing Lists / Github
Date: Fri, 11 Nov 2022 16:30:47 -0700 [thread overview]
Message-ID: <CAA_JP8XWLTe07bLJe6QOO4sy+Taw+-j1uFdLys834Z6GALUzeQ@mail.gmail.com> (raw)
In-Reply-To: <CAOZyJovDs9BoK++vvEqE3k0VwsF+BB0rvUq6hyVHSH4cWLDbXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
If we're voting, I'm going to go extreme. I will not use discord for
anything. I've been forced in the past and frankly, I'll never go back to
it. Discord is vile.
Slack or Telegraph is ok. I installed Matrix to see, @dandenson:matrix.org
, looks like I need an invite to that discussion.
On Fri, Nov 11, 2022 at 7:28 AM Robert Chacón via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Herbert and Toke,
>
> I've added you both now. 👍🏼
>
> On Fri, Nov 11, 2022 at 6:53 AM Herbert Wolverson via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
>> I'd never tried Matrix before, so I signed up as @herberticus:matrix.org.
>> It's telling me that I need a room invite.
>>
>> It's honestly kind-of funny. I'm on Discord for a bunch of Rust and
>> gamedev stuff (and a few personal friends),
>> Slack for my publisher, email, a whole bunch of Github discussions,
>> Mastodon and Twitter (to persuade people
>> to buy my books), Medium (publisher)... so they mostly get used
>> asynchronously like email in different
>> clients.
>>
>> On Fri, Nov 11, 2022 at 3:25 AM Toke Høiland-Jørgensen via LibreQoS <
>> libreqos@lists.bufferbloat.net> wrote:
>>
>>> Robert Chacón via LibreQoS <libreqos@lists.bufferbloat.net> writes:
>>>
>>> > Very cool! I really like it.
>>> > Here's a link to a Matrix LibreQoS room if anyone would like to join:
>>> > https://matrix.to/#/!HPuJeVMGSJchAqJqmN:matrix.org?via=matrix.org
>>>
>>> Can't seem to figure out how to get that link to actually work with my
>>> client; my Matrix handle is @toke:toke.dk if you'd care to invite me
>>> directly?
>>>
>>> -Toke
>>> _______________________________________________
>>> LibreQoS mailing list
>>> LibreQoS@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/libreqos
>>>
>> _______________________________________________
>> LibreQoS mailing list
>> LibreQoS@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/libreqos
>>
>
>
> --
> Robert Chacón
> CEO | JackRabbit Wireless LLC <http://jackrabbitwireless.com>
> Dev | LibreQoS.io
>
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 4260 bytes --]
next prev parent reply other threads:[~2022-11-11 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 2:19 Hayden Simon
2022-11-11 2:32 ` Dave Taht
2022-11-11 2:38 ` Robert Chacón
2022-11-11 2:40 ` Hayden Simon
2022-11-11 2:58 ` Dave Taht
2022-11-11 3:07 ` Robert Chacón
2022-11-11 3:09 ` Hayden Simon
2022-11-11 3:41 ` Dave Taht
2022-11-11 4:34 ` Dave Taht
2022-11-11 9:25 ` Toke Høiland-Jørgensen
2022-11-11 13:53 ` Herbert Wolverson
2022-11-11 14:28 ` Robert Chacón
2022-11-11 23:30 ` dan [this message]
2022-11-11 2:38 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA_JP8XWLTe07bLJe6QOO4sy+Taw+-j1uFdLys834Z6GALUzeQ@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=LibreQoS@lists.bufferbloat.net \
--cc=robert.chacon@jackrabbitwireless.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox