Il 07/08/19 19:30, Kathleen Moriarty ha scritto:
On Wed, Aug 7, 2019 at 1:26 PM Warren Kumari <warren@xxxxxxxxxx
<mailto:warren@xxxxxxxxxx>> wrote:
On Wed, Aug 7, 2019 at 4:10 AM Tim Chown <Tim.Chown@xxxxxxxxxx
<mailto:Tim.Chown@xxxxxxxxxx>> wrote:
>
> > On 7 Aug 2019, at 06:34, Mikael Abrahamsson <swmike@xxxxxxxxx
<mailto:swmike@xxxxxxxxx>> wrote:
> >
> > On Tue, 6 Aug 2019, Linda Dunbar wrote:
> >
> >> Installing Jabber is not easy. You have to find specific
servers to download, and very often you are not really sure which
one is legitimate.
> >
> > You do not need a Jabber client. You can use the WebRTC enabled
Meetecho webpage for the session and chat there. It's "the jabber
room". It nicely combines the jabber room (the chat window in
Meetecho), the video feed and the notes. It works in any modern
browser/OS on a desktop OS.
>
> Exactly; you can use MeetEcho to be "on Jabber".
>
Just a meta-note:
There are a large number of things where the answer is Meetecho -- I
think that we are at risk of forgetting just how much they have
improved our process / experience...
Would the network be impacted if signing onto meetecho became the norm
in the room?
Meetecho allows you to close all video feeds individually. So if you're
sitting in the room you can just close the slides and speaker feeds and
only use the integrated Jabber chat. The impact on the network would be
close to zero in this case.
Honest question.
Thanks,
Kathleen
W
> > I haven't used a jabber client to participate in IETF jabber
room for 3-5 years now. I only use Meetecho. I've jabber-scribed
probably 30 sessions this way.
>
> Same, though not so much scribing as professionals such as you :)
>
> Tim
>
--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
---maf
--
Best regards,
Kathleen