Exploring new communication channels


#41

This post was flagged by the community and is temporarily hidden.


#42

I think you misunderstand my point. I was arguing that the solution to @djc’s point is to make the same conversations accessible, simultaneously, from all platforms via bridging. Migrating at all is a failure mode, not a solution.


#43

I think you misunderstand my point. I was arguing that the solution to @djc’s point is to make the same conversations accessible, simultaneously, from all platforms via bridging. Migrating at all is a failure mode, not a solution.

This is a very theoretical point, as the chat system rosetta stone doesn’t exist and individual bridges bring a lot of maintenance with them. We would need a whole team of volunteers for that.


#44

Hi there! As an avid discord user (I use discord nearly constantly) I would be extremely disappointed if Rust switches to Discord.

The number one issue here is that Discord is 100% inaccessible, and the /r/blind team has been told it will stay that way.

For example, Discord has been rather rude to the /r/blind team, where /r/blind made a post on Discord’s subreddit asking if Discord will ever be accessible, and if not, they had custom clients that they could use. Discord responded by saying that using a custom client will get your account permanently banned from Discord and to contact them on Discord if they have more questions.

Discord has also said things to blind users like “get a better magnifier” and other things along that line. There has also been a support ticket open for (I think) about 4 years now asking for this, and there hasn’t been a single response from Discord.

Now, besides things like the above, there are other reasons I would prefer Rust doesn’t switch over to Discord. First off, the client is really terrible, with bugs nearly never getting fixed. The most often thing that will happen is Discord adds some half baked feature, makes a huge announcement for it, and then never fixes the bugs that come from it. Semi related is when a css change was pushed to the client without being checked, and it caused the “jump” buttons in the list of pinned messages to look completely wrong. It was about 24 hours before it was fixed.

Someone that would probably be less likely in the context of Rust, is the Discord community. From what I can tell since using Discord near constantly is that the majority of large communities on Discord is significantly more “toxic” than the ones on IRC or Slack. I’m not sure if something like this could come up for Rust, but it’s possible.

Discord also has a horrible terms of service. Custom css, custom clients, anything using your own Discord token, is completely forbidden, and will also get your account banned. On top of that, the API is horrible, with loads of inconsistencies and horrible documentation that is literally unreadable on mobile among other things.

I really really hope the Rust team(s) don’t decide to switch to Discord, it would ruin a lot of what I love about Rust for me.


#45

As others mentioned above, Mattermost (https://www.mattermost.org/) seems to be a solid alternative. In particular, Redox uses it for all their chat (https://chat.redox-os.org/redox/channels/town-square) and it seems to work well for that community.


#46

Another datapoint: using Mattermost at work (including a Matterbridge to an external Slack team), and it works just fine.


#47

This indeed sounds like a problem and something we should take quite seriously since a chief motivation in moving from IRC was to improve accessibility.


#48

Does anyone (r/blind for example) know if Mattermost is more accessible? Interesting thing to look into.

EDIT: Here are some links regarding Mattermost accessibility (I’m not expert enough on this topic to know if this is good or bad):

That last link might be the most informative.


#49

Was it really? I was under the impression that the variety of IRC clients made it possible to pick one that is compatible with whatever accessibility tools one might be using. (As opposed to systems that mandate a single client which may or may not work well in every situation.)


#50

I’m using “accessibility” (or rather “accessible”) in a more general sense here. For IRC the main problems are that you need bouncers and such to make IRC work well, which newcomers to IRC often don’t have. There’s https://www.irccloud.com/ but iirc it has some problems.


#51

I guess it’s worth mentioning that in this sense, IRC is inaccessible for me. I gave up on using the IRC channels many months ago, and I’m an IRC veteran that has auto-rejoin configured already (that is what everyone means by “bouncer”, right?). But the pervasive lack of what is now considered incredibly basic chat functionality, in particular any form of history (yes, we have bots for that, but they were literally broken more often than they worked) eventually made it impossible for me to actually participate in any meaningful discussions in those channels unless the conversation started after I got home from work and my internet was in such an exceptionally good mood that it never once bounced me. Which simply never happens.


#52

I pinged discord staff about this; accessibility is important. The toxicity thing is a per-community issue and doesn’t really apply to discord itself; IRC has the same, if not worse reputation, for example.

Regarding the accessibility issue,

Regarding TOS, they’ve only ever banned people who write bots who cause service outages.

So yeah, I’m not sure what issues you’ve had in the past, but it at least sounds like things may be different today.


#53

Yeah that… It is also common to have a setup with weechat + tmux on a server which you SSH into or use http://glowing-bear.org/ and some android app. I do this myself. The basic goal of all the varying solutions is to always be online and to never miss out on backlogs.


#54

So that we continue to have choice and reduce fragmentation, is there a reason we can’t keep the canonical source in IRC, and add bots to mirror the IRC channels with equivalent Gitter and Discord channels?

I’m especially bummed that net-wg suddenly switched to Discord, as I’m not going to keep yet another chat client open.


#55

There’s https://www.irccloud.com/ but iirc it has some problems.

IRCCloud, most notably, is a paid service to use it with the features we were discussing above (especially always-online).


#56

What’s wrong with Slack for text conversation?

Discord is nice for gamers, not for programmers. It’s game focused (twitch, facebook integrations, game statuses, voice channels). Overall UI is… inconvenient in comparison with text based chats (Github, Gitter, Slack, HipChat, what else?).

Telegram (Viber, whatsapp, fbchat, etc) is a phone chat, it’s definitely out of league here.


#57

Right; I think those were the problems I had in mind. Thanks!


#58

That’s a big loss! That’s also where the futures team is doing a lot of their communication, and we’ve been hoping to add you to that team as well. Is there any chance you would reconsider the cost/benefit here?


#59

I’ll investigate if I can set up a personal connect-to-discord-via-IRC thingy.

However, continuing what I suggested: there appears to be a tool, discord-irc, which mirrors various IRC channels and Discord channels. Could this be used so that people who prefer Discord’s UI can use that, and others who prefer IRC can use it? Serious question. As an example, the whatever-the-net-wg-discord-channel-name can be mirrored to irc.mozilla.org/rust-net-wg.


#60

no need for an IRC bridge, just connect using the browser. or a dedicated matrix client.