Rust for Linux List
 help / color / mirror / Atom feed
From: Wedson Almeida Filho <wedsonaf@google.com>
To: Geert Stappers <stappers@stappers.nl>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	"comex ." <comexk@gmail.com>,
	rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Video conferencing platform choice
Date: Tue, 20 Apr 2021 20:50:40 +0100	[thread overview]
Message-ID: <YH8wkC4IAfSu6sk+@google.com> (raw)
In-Reply-To: <20210420192936.6kxvgn2l6zsnmgaq@gpm.stappers.nl>

I'm running a test session for the next 20min or so. If anyone else would like
to test, ping me and I'll share the address privately.

Cheers,
-Wedson

On Tue, Apr 20, 2021 at 09:29:36PM +0200, Geert Stappers wrote:
> On Tue, Apr 20, 2021 at 07:32:39PM +0200, Miguel Ojeda wrote:
> > On Tue, Apr 20, 2021 at 7:25 PM comex . <comexk@gmail.com> wrote:
> > >
> > > What is v1d30?  Googling it does not bring up anything relevant-looking.
> > 
> > Good question -- I have not used it.
> > 
> > Geert, could you please give us some details? Thank you!
> > 
> 
> The server side software is Big Blue Button.
> Documentation at https://docs.bigbluebutton.org/
> 
> People of v1d30, video vowels became numbers,
> have video conferencing service as business model.
> Their website is https://v1d30.net/
> 
> It is the user expirence I appreciate:
> * Visit website
> * Enter "Handle" or "Nick name"
> * Continue    (no need for password or other account hassle)
> * Check of your microfoon  (without bothering people in the "room")
> * Entering the room
> * Choice on using camera (no package deal with choosing micro phone)
> 
> 
> 
> 
> In-Reply-To: <CAMKQLN+t1yyOeptSRQBzw=1pCV4CML4WSxV9Q4s_cyi6c4-P6A@mail.gmail.com>
> On Tue, Apr 20, 2021 at 06:35:22PM +0100, Wedson Almeida Filho wrote:
> > Geert,
> > 
> > Do you have specific concerns or just want to try something different?
> > (I'm happy if you respond privately if you'd prefer.)
> > 
> > If it's about having a google account,
> 
> Both "account" and "google account".
> 
> Account is pub versus club. Just going the pub, not first becoming
> member before being allowed to enter the club.
> 
> Google account is "be one of billions". It makes me feel lost.
> 
> 
> > I just tested it and you don't need one to join a session.
> 
> I'm happy to test it from my site of the Internet. My test setup
> is from outside Google employee network, webbrowser without Google
> account cookie.
> 
> My main reason for testing is to reproduce the account login
> that I got at the previous Rust for Linux meeting at Google Meet.
> 
> I'm in UTC+2 and awake till 20:30 UTC for "login" test.
> 
> 
> 
> Groeten
> Geert Stappers
> -- 
> Silence is hard to parse

  reply	other threads:[~2021-04-20 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 17:21 Video conferencing platform choice Miguel Ojeda
2021-04-20 17:25 ` comex .
2021-04-20 17:32   ` Miguel Ojeda
2021-04-20 19:29     ` Geert Stappers
2021-04-20 19:50       ` Wedson Almeida Filho [this message]
2021-04-20 20:26 ` Josh Triplett
     [not found] ` <CAFRnB2XSjvuOU4SxokN5R6171PhD83R6=pOiv=ksNe58TyMpmw@mail.gmail.com>
2021-04-20 20:28   ` Geert Stappers

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=YH8wkC4IAfSu6sk+@google.com \
    --to=wedsonaf@google.com \
    --cc=comexk@gmail.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stappers@stappers.nl \
    /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