From: Yasuaki Kudo <yasu@yasuaki.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Jitsi Meet Screen Sharing with Ungoogled-Chromium
Date: Mon, 17 Jan 2022 11:34:54 +0900 [thread overview]
Message-ID: <3C319344-5B5D-4C47-9288-3D3CCD36C6DA@yasuaki.com> (raw)
In-Reply-To: <87sftnw8y6.fsf@elephly.net>
Thank you much for your replies and I believe Jacob was just making a joke and I am in no way offended! But thank you Ricardo 😄😄 I hope this bug gets fixed!
PS
For various issues of conviction, of which Free Software is one, I believe we need to have open playful attitudes to the opposition (e.g. people who don't give a damn about software freedom) a, if only to have more effective strategies by understanding them. I was just watching this this morning https://youtu.be/Blz_Eu00Kbw 😄
-Yasu
> On Jan 17, 2022, at 08:35, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Jacob Hrbek <kreyren@rixotstudio.cz> writes:
>
>> [[PGP Signed Part:Undecided]]
>>> Third party not a guix package
>>
>> Those are not supported by GNU Guix and will be met with hostility,
>> because how dare you unfree scum!
>
> Jacob, this style of communication is not acceptable on this mailing
> list.
>
> It is also not true.
>
> --
> Ricardo
>
next prev parent reply other threads:[~2022-01-17 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 9:46 Jitsi Meet Screen Sharing with Ungoogled-Chromium Yasuaki Kudo
2022-01-16 10:24 ` Jacob Hrbek
2022-01-16 10:27 ` bug#53301: Ungoogled-chromium lacks VP8 codec support preventing jitsi screensharing Jacob Hrbek
2022-01-16 10:30 ` Jacob Hrbek
2022-01-17 17:35 ` Marius Bakke
2022-01-16 23:34 ` Jitsi Meet Screen Sharing with Ungoogled-Chromium Ricardo Wurmus
2022-01-17 2:34 ` Yasuaki Kudo [this message]
2022-01-16 10:34 ` Jacob Hrbek
2022-01-16 10:34 ` Remco
2022-01-16 11:25 ` Sergiu Ivanov
2022-01-16 12:26 ` Jacob Hrbek
2022-01-20 16:55 ` Remco
2022-01-21 15:23 ` Yasuaki Kudo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C319344-5B5D-4C47-9288-3D3CCD36C6DA@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.