# Mozilla leaving IRC

**URL:** <https://discourse.mozilla.org/t/mozilla-leaving-irc/38721>\
**Category:** Mozillians\
**Created:** [April 27, 2019, 8:14pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721 "2019-04-27T20:14:30Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![amir.farsi](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/amir.farsi/32/23678_2.png) [@amir.farsi](https://discourse.mozilla.org/u/amir.farsi)\
**Post date:** [April 27, 2019, 8:14pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/1 "2019-04-27T20:14:30Z")

</div>

Hello dear mozillians.  
I saw this link on Mike Hoy’s blog that says mozilla will leave IRC as it’s communication method.  
[http://exple.tive.org/blarg/2019/04/26/synchronous-text/](http://exple.tive.org/blarg/2019/04/26/synchronous-text/)

It seems it’s serious. Lets talk about it here, on this post.  
What is your opinion? I think Mozillians as end users of new chat system should participate in process of selection replacement of IRC for Mozilla. However fianlly, Mr Mike Hoye, will decide what to choose?  
Do you think newer IRC version, named IRC v3 can help and solve the problem mentioned in that blog post? Look at: [https://ircv3.net](https://ircv3.net)

Lets list the potential replacements:

1. Telegram

- Telegram is open source but it’s core server side isn’t fully open source

- Telegram’s bots can help to apply [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/)

- Telegram is blocked by some countries like Iran and Russia and Users f these countries should use VPN,… to use it

- Telegram Blocked Public groups with uniqe id for some countries like Iran by check the user’s phone number not ip address. As result members of Persian SUMO team can’t join to [http://t.me/mozsumo](http://t.me/mozsumo) public group, even by using VPN. However we can join to Telegram Supergroups that haven’t unique short user name like L10n Telegram super group.

2-Discord

- Discord desined mainly for gamers, it’s not fully like Slack.
- Discord isn’t Open Source

3-Slack

- Slack can support bots to apply [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/)
- Slack isn’t Open Source

---

<div class="post-metadata">

**Author:** ![exe-boss](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/exe-boss/32/43293_2.png) [@exe-boss](https://discourse.mozilla.org/u/exe-boss)\
**Post date:** [April 27, 2019, 9:15pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/2 "2019-04-27T21:15:25Z")

</div>

I sure hope so.

I already made [NOVA](https://NOVA-Team.GitHub.io) switch to&nbsp;using [Discord](https://DiscordApp.com) because of&nbsp;how much I&nbsp;hate IRC due to&nbsp;how horribly painful it&nbsp;is&nbsp;to&nbsp;use and how terribly outdated the&nbsp;protocol and&nbsp;UX&nbsp;is.

---

<div class="post-metadata">

**Author:** ![alex\_mayorga](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@alex\_mayorga](https://discourse.mozilla.org/u/alex_mayorga)\
**Post date:** [April 28, 2019, 6:50pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/3 "2019-04-28T18:50:48Z")

</div>

¡Hola @amir.farsi!

I don’t believe that @mhoye would be making this decision as an individual here.

I’ve seen the bot spam problems of recently in both IRC and Telegram, although I must say it seems to be more prevalent on the later than the former AFAICT.

There was a typo in the link to the Telegram SUMO group, the right one is [https://t.me/mozsumo](https://t.me/mozsumo)

I’m just hopping that whatever is eventually chosen is something I could connect with as easily or as difficultly as to IRC on my current favorite client [https://riot.im/](https://riot.im/)

¡Gracias!  
Alex

---

<div class="post-metadata">

**Author:** ![irvin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/irvin/32/59482_2.png) [@irvin](https://discourse.mozilla.org/u/irvin)\
**Post date:** [April 29, 2019, 6:07am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/4 "2019-04-29T06:07:10Z")

</div>

Most of the Mozilla team’s daily operation is already on Slack and not open to the public (anymore?) so I wonder which team will be affected?

---

<div class="post-metadata">

**Author:** ![alberts](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/alberts/32/22591_2.png) [@alberts](https://discourse.mozilla.org/u/alberts)\
**Post date:** [April 29, 2019, 11:41am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/5 "2019-04-29T11:41:47Z")

</div>

Also hoping for a move to [Matrix](https://matrix.org/) (Riot)!

---

<div class="post-metadata">

**Author:** ![mhoye](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mhoye](https://discourse.mozilla.org/u/mhoye)\
**Post date:** [April 29, 2019, 4:35pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/6 "2019-04-29T16:35:46Z")

</div>

Hi, everyone - @mhoye here.

@alex_mayorga is right that this isn’t a unilateral decision on my part. That said, we have a number of good choices here - I’m going to be posting more about that shortly - and I’m happy to talk here about what we’re trying to accomplish and what success looks like.

---

<div class="post-metadata">

**Author:** ![mhoye](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mhoye](https://discourse.mozilla.org/u/mhoye)\
**Post date:** [April 29, 2019, 7:28pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/7 "2019-04-29T19:28:30Z")

</div>

I should add, there’s a #synchronicity channel on both IRC and Slack for this as well.

---

<div class="post-metadata">

**Author:** ![mischmerz](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@mischmerz](https://discourse.mozilla.org/u/mischmerz)\
**Post date:** [May 4, 2019, 6:14pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/8 "2019-05-04T18:14:11Z")

</div>

I understand the limitations with IRC. But IRC is also an easy to use, easy to implement, open source environment. If push comes to shove you can write a client in a few lines of code or even use telnet to connect to it. What is the urgency to get rid of a proven and stabile protocol and environment? Any other platform - if as open to the public as IRC - will be as difficult to manage as IRC is. It is extremely simply to write bots that require some form of identification - even non IRC methods - to be allowed to join a channel (or be kicked right after joining) . I dare to say there’s not a single environment that is so robust, flexible and battle hardened as IRC when it comes to communications.

Mke writes:

“RC is an ongoing source of abuse and harassment for many of our colleagues.”

(1) Every “open to the public” platform unfortunately has these problems. Bots can be used to effectively police channels.

“…getting connected to this now-obscure forum is an unnecessary technical barrier for anyone finding their way to Mozilla via the web.”

(2) There are plenty of web gateways to IRC. It’s the most simple protocol to implement and the development of a web-client is trivial

“Available interfaces really haven’t kept up with modern expectations …”

See (2)

"… spambots and harassment are endemic to the platform … "

See (1)

“… and in light of that it’s no coincidence that people trying to get in touch with us from inside schools, colleges or corporate networks are finding that often as not IRC traffic isn’t allowed past institutional firewalls at all.”

See (2) - Additionally: There’s nothing that says you can’t have an IRC server on port 443.

All in all I don’t find the reasons for the abandonment of IRC convincing. So - I wonder - are there other reasons to move?

---

<div class="post-metadata">

**Author:** ![SJW](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@SJW](https://discourse.mozilla.org/u/SJW)\
**Post date:** [May 4, 2019, 10:15pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/9 "2019-05-04T22:15:34Z")

</div>

IRC is very handy, FLOSS and works on any platform. These should also be the criteria for a replacement.

Here are some FLOSS alternatives:

> **[Wire – Collaborate without Compromise](https://wire.com/en/)**
>
> Collaborate without compromise with Wire, the trusted platform for millions worldwide. Stay in control with end-to-end encryption that's invisible, flexible collaboration, and intuitive user interface. Join now for free and boost your productivity.

> **[Rocket.Chat: Communications Platform You Can Fully Trust](https://www.rocket.chat/)**
>
> Explore Rocket.Chat, where we put data privacy into every conversation and enable teams to collaborate seamlessly.

> **[Mattermost | Secure Collaboration for Technical Teams](https://mattermost.com/?redirect_source=mm-org)**
>
> Accelerate mission critical work in complex environments with a customizable, self-sovereign collaboration hub.

Any homebrew solution based on WebRTC?

---

<div class="post-metadata">

**Author:** ![mhoye](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mhoye](https://discourse.mozilla.org/u/mhoye)\
**Post date:** [May 7, 2019, 2:42pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/10 "2019-05-07T14:42:34Z")

</div>

_Every “open to the public” platform unfortunately has these problems._

This is, unfortunately, one of the most common arguments against changing; at the very least, conceding that it’s true amounts to surrendering, of giving up on the idea that safety and civility on an open network. I just flat out refuse to believe it’s true.

We need to stop talking about harassment and abuse on the network as though it’s inevitable, and start talking about it as though it’s inexcusable.

---

<div class="post-metadata">

**Author:** ![Svetlana](https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/32.png) [@Svetlana](https://discourse.mozilla.org/u/Svetlana)\
**Post date:** [June 20, 2019, 1:41am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/11 "2019-06-20T01:41:11Z")

</div>

I think there are some user friendly options for IRC, such as [http://convos.by](http://convos.by), [http://glowing-bear.org](http://glowing-bear.org), or if you can install things then I find [http://quassel-irc.org](http://quassel-irc.org) a bit awesome.

See also [www.kiwiirc.com](http://www.kiwiirc.com), and www.thelounge.chat

I like that unlike discord IRC is in real time and the potential for mentoring or troubleshooting is greatly increased.

I hope [irc.mozilla.org](http://irc.mozilla.org) can continue to exist on unofficial basis run by volunteers in the case Mozilla drops official support.

---

<div class="post-metadata">

**Author:** ![tanner](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/tanner/32/30590_2.png) [@tanner](https://discourse.mozilla.org/u/tanner)\
**Post date:** [June 20, 2019, 5:20am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/12 "2019-06-20T05:20:17Z")

</div>

> [@Svetlana](#):
>
> I like that unlike discord IRC is in real time and the potential for mentoring or troubleshooting is greatly increased.

I’m not sure what you mean by that. Discord _is_ in real-time. But I don’t think Discord is the way to move forward.

> [@Svetlana](#):
>
> I hope [irc.mozilla.org](http://irc.mozilla.org) can continue to exist on unofficial basis run by volunteers in the case Mozilla drops official support.

I can’t see that happening. There’d be a lot of resources that would have to be put into that, and I don’t think anyone really has them.

As @mhoye’s post says, IRC hasn’t kept up with the times. It’s ridiculously easy to abuse people on it, and we ~~shouldn’t~~ cannot take the “oh well, boys will be boys” stance. I don’t think that being open and being safe are mutually exclusive, but IRC sure makes it look like they are. We can do better.

---

<div class="post-metadata">

**Author:** ![net333](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/net333/32/28215_2.png) [@net333](https://discourse.mozilla.org/u/net333)\
**Post date:** [June 24, 2019, 10:21am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/13 "2019-06-24T10:21:32Z")

</div>

> While we’re investigating options for semi-anonymous or pseudonymous connections, we will require authentication, because:  
> The Mozilla Community Participation Guidelines will apply, and they’ll be enforced.

In the Guidelines I did not find rules pertaining to authenticating. Am I missing sth.?

---

<div class="post-metadata">

**Author:** ![net333](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/net333/32/28215_2.png) [@net333](https://discourse.mozilla.org/u/net333)\
**Post date:** [June 24, 2019, 10:26am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/14 "2019-06-24T10:26:02Z")

</div>

Since security is appearantly a big issue here, why not ask **NSA** to host the Mozilla chat server outright? A transparent move, no?

---

<div class="post-metadata">

**Author:** ![nukeador](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/nukeador/32/20533_2.png) [@nukeador](https://discourse.mozilla.org/u/nukeador)\
**Post date:** [June 24, 2019, 11:48pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/15 "2019-06-24T23:48:16Z")

</div>

There are two considerations here from my point of view.

- Un-Authenticated users are hard or nearly impossible to moderate efficiently (this very forum requires log-in)
- Authenticated systems can be anonymous if you use an email that can’t be associated with a person, and that’s fine.

---

<div class="post-metadata">

**Author:** ![net333](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/net333/32/28215_2.png) [@net333](https://discourse.mozilla.org/u/net333)\
**Post date:** [June 25, 2019, 3:57pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/16 "2019-06-25T15:57:13Z")

</div>

And then there is

- bad authentication requiring a whole lot of hoop-jumping and
- less tedious auth…

MS shows how to scare users away with their dreaded **iron-fist-policy** regarding Auth. Let’s hope Mozilla is smarter than MS.

---

<div class="post-metadata">

**Author:** ![nukeador](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/nukeador/32/20533_2.png) [@nukeador](https://discourse.mozilla.org/u/nukeador)\
**Post date:** [June 26, 2019, 11:30am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/17 "2019-06-26T11:30:58Z")

</div>

Can you elaborate what do you consider tedious about Mozilla’s authentication system? #iam team can use your feedback to improve.

---

<div class="post-metadata">

**Author:** ![net333](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/net333/32/28215_2.png) [@net333](https://discourse.mozilla.org/u/net333)\
**Post date:** [July 2, 2019, 7:21am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/18 "2019-07-02T07:21:58Z")

</div>

getting in here with the KDE Falkon browser took me 2 runs via e-mail. I thought it would not work at all.

---

<div class="post-metadata">

**Author:** ![rcmainak](https://avatars.discourse-cdn.com/v4/letter/r/e274bd/32.png) [@rcmainak](https://discourse.mozilla.org/u/rcmainak)\
**Post date:** [July 5, 2019, 12:30pm UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/19 "2019-07-05T12:30:51Z")

</div>

Hopefully we don’t end up choosing a locked down propriety solution. There are many open source modern alternatives such as [mattermost](https://www.mattermost.org/) or [matrix](https://matrix.org/).

[I would like to mention that recently KDE community was also looking for alternative and they choose matrix as their communication platform](https://dot.kde.org/2019/02/20/kde-adding-matrix-its-im-framework). I hope we can learn a thing or two from the KDE community as well.

---

<div class="post-metadata">

**Author:** ![pdurbin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/pdurbin/32/29495_2.png) [@pdurbin](https://discourse.mozilla.org/u/pdurbin)\
**Post date:** [September 13, 2019, 10:36am UTC](https://discourse.mozilla.org/t/mozilla-leaving-irc/38721/20 "2019-09-13T10:36:04Z")

</div>

There’s a new post at [Synchronous Messaging at Mozilla - Trial Servers & Feedback](https://discourse.mozilla.org/t/synchronous-messaging-at-mozilla-trial-servers-feedback/44871) that explains the candidate synchronous messaging stacks and asks us to try them out and give feedback.