From: Mauro Carvalho Chehab <maurochehab@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-media@vger.kernel.org
Subject: LinuxTV IRC channels
Date: Thu, 20 May 2021 10:56:26 +0200 [thread overview]
Message-ID: <20210520105626.00802e5d@coco.lan> (raw)
Hi,
Probably some of you already read some news about Freenode, like those:
https://www.phoronix.com/scan.php?page=news_item&px=Free-Software-Exits-Freenode
https://lwn.net/Articles/856543
It sounds too early to take any decisions about that, as we need to
wait for things to calm down in order to take any decisions that
could impact our community.
Yet, as concerns regarding privacy could be real, I'd like to remind
you that:
1. we use the IRC chat channels at Freenode (#v4l and #linuxtv) on
our public discussions.
As such, those channels (either at Freenode or on any other IRC server)
shouldn't be used to discuss sensitive information or to expose data
that could compromise personal information;
2. only the server owners could ensure that information exchanged via
a chat platform is secure;
3. The LinuxTV community doesn't own any servers. So, there's no
warranty - either explicit or implicit - that any information
posted there would be kept in private, even if exchanged via
private messages.
On other words, only use chat channels for information that aren't
sensitive. Also, use private messages at your own risk. From my side,
I recommend you to not discuss any sensitive information via IRC ;-)
The media maintainers are following closely what's happening with
Freenode and, while we registered some channels at Libera.chat
(to where several Freenode operator volunteers moded), for now,
we're keep using #v4l and #linuxtv channels at Freenode.
If something changes, we'll let you know via e-mail.
reply other threads:[~2021-05-20 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210520105626.00802e5d@coco.lan \
--to=maurochehab@gmail.com \
--cc=linux-media@vger.kernel.org \
/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 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.