I spend as close to zero time on slack as possible, because it is such a time sink. But to your point, yes, IETF could run its own jabber server, and I've suggested that before (previous IETFs, as well as earlier in this conversation), but gotten no response. I think part of the problem is that setting up a jabber server isn't trivial, and isn't something most people have done. It's possible that if someone (you?) who has already climbed that learning curve were willing to do it, this could be solved quickly.
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. Plus it consumes bandwidth even if you don't need the AV feed.
On Mon, Nov 12, 2018 at 2:14 PM Peter Saint-Andre <stpeter@xxxxxxxxxxx> wrote:
On 11/12/18 11:12 AM, Ted Lemon wrote:
> Slack lets you archive discussions.
As long as the provider meets IETF policies on control over the
archives, that's great.
> Not that I'm suggesting using
> Slack;
We can use whatever meets the requirements we have, I suppose.
> I'm just pointing out reasons why Jabber hasn't taken off, and
> why it's not working for us.
Those are two different questions.
> Federation _is_ mandatory, in the sense
> that I can't join an IETF jabber room without it.
The IETF could run its own Jabber server, or registered attendees could
use Meetecho as described earlier in this thread.
> I think there's a larger problem to be looked at here, of which this
> particular point is one aspect. It would be good to write something
> up. At the same time, it's a time sink, and I don't have any slack
> time right now in which to do it. :(
If you spent less time on Slack, you might have more slack time. ;-)
Peter
