Re: Jabber [Was: Plenary questions]

[Ted Lemon <[e-mail]>]

FWIW, the problem with meetecho as a local jabber tool is not that it's
impossible to access it.   It's that it's not the right tool.   You have to
jump through hoops to use it, and then you wind up getting stuff you don't
need that needlessly consumes bandwidth and possibly causes feedback if you
don't mute your speaker.   The experience I reported of being "unable to
access jabber through meetecho" was really that combination of factors
arising in consciousness as a great big "nope" when I looked at the sign-in
screen.   I'm sorry if the way I reported it earlier made it out to be the
case that meetecho wasn't working—that really wasn't the point I was trying
to communicate.

On Tue, Nov 13, 2018 at 9:28 AM Daniele Ceccarelli <
[e-mail]> wrote:

> Hi,
>
> > -----Original Message-----
> > From: ietf <[e-mail]> On Behalf Of Alessandro Amirante
> > Sent: martedì 13 novembre 2018 09:50
> > To: Ted Lemon <[e-mail]>; [e-mail]
> > Cc: Paul Wouters <[e-mail]>; ietf <[e-mail]>
> > Subject: Re: Jabber [Was: Plenary questions]
> >
> > Il 12/11/18 20:16, Ted Lemon ha scritto:
> > > The Meetecho server is a lousy choice.   I tried using it this IETF,
> > > and it demanded all kinds of authentication information I didn't have
> > > handy.
> >
> > Meetecho is a tool for *participating* remotely at IETF meetings. It
> allows
> > you to actively contribute to the standardization process. As such, it
> requires
> > you to be registered to the IETF meeting (either as on-site or remote
> > participant) because you need to be identifiable and accept the "Note
> Well"
> > (which you do during the registration process).
> >
> > All authentication information you need is your name and your
> Registration
> > ID, which is also printed on your badge if you're a local participant.
> There's
> > also a clear way to retrieve it through the registration system.
>
> [>DC] I joined the Meetecho session during the session I was chairing.
> Obviously I didn't have my registration number at hand (I didn't notice it
> was on the badge) when asked for it but it took me 5 seconds to ask to have
> it re-sent by email. I couldn't ask for anything faster and easier than
> that.
>
> BR
> Daniele
>
> >
> > > Plus it consumes bandwidth even if you don't need the AV feed.
> >
> > Video feeds can be disabled from within the Meetecho UI. Audio can't.
> > Anyway I do agree that using Meetecho only as a Jabber client is far from
> > ideal and overkill. There are XMPP clients for that.
> >
> > Alessandro
>
>