My company and association, credil.org, uses XMPP, and we maintain a server. I use pidgin, and I will continue to use it. I tried to zulip stuff during IETF114, and I found it distracting, hard to interact with, and in most cases, as a result, I did not participate that way. I have remained in the "hallway" XMPP conference since sometime in 2012, reachable at any time. The number of people who just logged in to that channel has gone from me and another guy, to twenty or thirty people. That will go away. I don't think that I any intention of opening another tab, and another Gb of ram for zulip. I am actively hostile to using slack for this reason. I run lots and lots of "native" clients for multiple systems, many of which turn out to be thin wrappers around chrome clients, which also annoys me a great deal. I sure hope that this will go away. So for the IETF and for me, this transition is a loss. I think that the problems of maintaining a client for your favourite desktop platform is largely overblown. Yes, a few people found it difficult, and they didn't like the clients that had support. What privilege to expect to have a freely downloadable client with support. I also think that finding a server wasn't really that hard. And frankly, for 90% of people, they only ever used the service when the meeting was in progress, in which case using the one built-in to meetecho was probably just fine. (I didn't like it, mind you) I didn't know we were going to get rid of the bridges. Had I known that, I would have protested harder, and kicked the zulip tires until broke. I just figured that choices were good, and that zulip wasn't a choice for me, but that was okay... because choices. I'm very sad. -- Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works -= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
