# Exploring new communication channels

**URL:** <https://internals.rust-lang.org/t/exploring-new-communication-channels/7859>\
**Category:** announcements\
**Created:** [July 3, 2018, 11:30pm UTC](https://internals.rust-lang.org/t/exploring-new-communication-channels/7859 "2018-07-03T23:30:55Z")\
**Posts on this page:** 1\
**Showing post:** 138

<div class="post-metadata">

**Author:** ![rishig](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/rishig/32/4601_2.png) [@rishig](https://internals.rust-lang.org/u/rishig)\
**Post date:** [August 23, 2018, 7:07pm UTC](https://internals.rust-lang.org/t/exploring-new-communication-channels/7859/138 "2018-08-23T19:07:26Z")

</div>

Hi, Zulip developer here. At the risk of cross-posting with [Where should the compiler team (and perhaps working groups) chat?](https://internals.rust-lang.org/t/where-should-the-compiler-team-and-perhaps-working-groups-chat/7894/37), I just wanted to offer support, and answer any questions you may have about Zulip.

To answer some of the questions from this thread:

- Business model: We sell hosting on [zulipchat.com](http://zulipchat.com), and enterprise support for on-premise deployments: [https://zulipchat.com/plans/](https://zulipchat.com/plans/).

- Deleting of threads: Admins can delete messages and ban users, and also rename threads. Zulip threads are meant to be ephemeral, with the moderation (by design) happening on streams, messages, and users.

- Vendor lock-in: Zulip runs both in the cloud and on-premise, and we provide full exports: [https://zulipchat.com/help/export-your-organization](https://zulipchat.com/help/export-your-organization). The on-premise product is the same as the SAAS product, and there is no proprietary code (so e.g. running Zulip locally doesn’t need a a license.)

- Mobile: We’re working on it. We’ve put a lot of work on it since the beginning of the summer, and are going to continue to do so. The current version (released today) is already a lot more reliable than the version in July, and I use it pretty heavily when travelling.

- Bridging: It’s hard to satisfactorily bridge Zulip with IRC or Discord, due to the different conversation models, but we do bridge with email.

For accessibility: I suspect we’re considerably farther along than Discord is, and our goal is to make the main webapp a great experience for blind users. We’re not there yet, but I think we’ve gotten the basic framework right, and getting to good accessibility won’t involve throwing out lots of html.

Some things we have made a lot of progress on in the accessibility space are:

- Nearly everything in Zulip can be navigated via the keyboard (many of the developers of Zulip exclusively navigate Zulip from the keyboard, at this point).

- We have a terminal client (in alpha, but all of the basic functionality is there, and we’d love feedback).

- We bridge with email. It doesn’t support things like emoji reactions, but the basic “read and reply” functionality is there.

I’ll be checking this thread for a bit, but also feel free to find me on [https://chat.zulip.org](https://chat.zulip.org) (Zulip community server) or at [support@zulipchat.com](mailto:support@zulipchat.com) at any time.

---

_[View the full topic](https://internals.rust-lang.org/t/exploring-new-communication-channels/7859)._