From: Yuchen Pei <id@ypei.org>
To: Andy Tai <atai@atai.org>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Fwd: We Call on FOSS Contributors to “Exit Zoom”
Date: Thu, 17 Aug 2023 23:49:04 +1000 [thread overview]
Message-ID: <87y1i97p9r.fsf@ypei.org> (raw)
In-Reply-To: <CAJsg1E_NLGFn9LUcpDC7y7yY1bn1rrJjjAjd6-52SaRfT2RdNA@mail.gmail.com> (Andy Tai's message of "Tue, 15 Aug 2023 13:19:41 -0700")
On Tue 2023-08-15 13:19:41 -0700, Andy Tai wrote:
> We considered completely avoiding those meetings in protest. However, we
> saw the same pressure that every individual feels when presented with a
> Zoom link: you miss the chance to even participate in the dialogue, and
> in some cases, you even risk losing your job! As a compromise for our
> situation, SFC staff took an activist approach. We insist on joining
> those meetings solely by phone — allowing us to use our mostly-FOSS
> LineageOS mobile devices.
I've been joining zoom meetings from my phone. It does not take away any
of my user freedom, but there's still the privacy issue.
> This strategy had benefits and downsides. Sometimes, being the only
> participant without video sparked interesting discussion about avoidance
> of proprietary and centralized platforms was an essential part of
> advocating for ethical technology. Participants on those calls, often
> acknowledged that on a high level the issues we raised were important,
> even if they weren't ready to make a change immediately. Other times, we
> were made to feel “othered” because we weren't appearing on video and
> had no visual clues about what was happening in the meeting. That
> feeling is difficult for anyone to endure, even while we stood steadfast
> in our principles.
I can remember two more issues when joining by phone, one is you don't
see anyone raising their hands, and you don't know where you are in the
queue to speak. By from my experience if people are ok for you to join
by phone, they normally understand if you speak out of order. Another
issue is if you, like me, have a non-biblical/"Western" name it could be
hard for people to remember as they can't see the name from the screen.
Best,
Yuchen
--
Timezone: UTC+10
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
<https://ypei.org/assets/ypei-pubkey.txt>
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
prev parent reply other threads:[~2023-08-17 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZNvP5NsxnLACB0zL@wn>
2023-08-15 20:19 ` Fwd: We Call on FOSS Contributors to “Exit Zoom” Andy Tai
2023-08-17 13:49 ` Yuchen Pei [this message]
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.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1i97p9r.fsf@ypei.org \
--to=id@ypei.org \
--cc=atai@atai.org \
--cc=libreplanet-discuss@libreplanet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).