Re: IETF Slack workspace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Aug 28, 2020, at 3:12 PM, Michael Richardson <mcr+ietf@xxxxxxxxxxxx> wrote:
> 
> 
> It feels like a major argument for slack is that offers reliable sign up for
> people who don't know how to find a jabber server, and/or who are unable to
> run an XMPP client.

There’s also the fact that Jabber and the multiple device presence issues make it easy for a message to be lost, or unknown if it’s actually received.  It will silently fail, and we should not expect participants in the IETF to be able to run, troubleshoot and repair a XMPP server and client set.

>  I use pidgin/libpurple, and I know that there were times
> when there were significant security issues with it.  I've heard that on
> Mac that there is not really a (thick) client that has reasonable support.

There is also the spam problem.  And if you blacklist, greylist or whitelist domains, you have the problems above.

> So it seems to me that:
> 1) the IETF should run a jabber server to which we can register to using
>   our DT login. (through OpenID Connect, I guess)

This would make some sense, but then username@domain@xxxxxxxxxxxxxxx ?

> 2) that the IETF should host one or more web based XMPP clients, possibly
>   paying a license fee/support.
> 
> Slack supported XMPP in/out when it first launched, but then stopped.
> I've been told that this is actually configurable on a per-workspace basis.
> I don't know the truth of this.

This has it’s own issues, because their XMPP support didn’t notify you of channels you were added to, leading to the blind messaging problem above.

> It would ideal if Slack could XMPP s2s out to IETF jabber servers, but
> I would not be surprised if this is not supported.

Slack model is on a pay per user model (primarily), so s2s on XMPP is not going to work right.

You can integrate slack workspaces together, lets say you have one called example1 and example2, you can link them and have shared channels.  This doesn’t really match the IETF communication model.

I have to say this:

If my kids can figure out how to do this and the IETF can’t, we’re clearly missing something, or attempting to over-engineer or over-religion it.

- Jared





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux