Live data from Hacker News

Please don't use Slack for FOSS projects (2015)

drewdevault.com

11–20 of 136 posts

Re: Please don't use Slack for FOSS projects (2015)

#11
post #3

Funny to see this reposted today, as just today I encountered an open source project which primarily uses Discord for chat - a terrible idea for all the same reasons. I had planned on writing a similar follow-up article reminding people that Discord is a bad communication medium for open source projects, too. I think that this is something the community ought to be occasionally reminded of, lest we lapse.

What's wrong with Discord?

Replace "slack" in that article with "discord"

Re: Please don't use Slack for FOSS projects (2015)

#12
post #6

There have been months where the spam on freenode was unbearable, and fundamentally IRC is, like SMTP, a protocol where spammers have the advantage, and only heuristics stop spam. A big part of the value of IRC-replacements are accounts that are tied enough to a person's identity (For example, by requiring sms confirmation) to deter most spam. IRC hasn't been able to do that.

Doesn't IRC support the registration of usernames?

No.

Individual IRC server implementations might, but each implementation seems to be unique in how they handle it (maybe through a website, maybe through NickServ, maybe through AuthServ, maybe through yet another bot name, and login may or may not use the PASS command, etc.), and those implementations frequently have you jumping through brittle hoops to auth that break when you attempt to automate them due to timing issues etc. leaving you manually logging in every time.

Which is probably part of the reason why the IRC servers I can think of generally all allowed messaging without any kind of registration other than connecting and auto-choosing a unique-for-now nickname. IRC moderation then becomes an uncoordinated, individualized, constant game of whack-a-proxy, RBLs, etc.

Re: Please don't use Slack for FOSS projects (2015)

#13
Acting like IRC is equal in functionality to Slack or Discord is straight up delusional.

One of the biggest problems with IRC is that there is no immediately obvious way to jump into a channel and browse or search the history.

Also, because there are so many IRC clients, and so many servers out there, one person's IRC experience can vastly differ from another's.

IRC also doesn't have any of the modern amenities like emoji reactions or reaction gifs, comment threads, code snippets, plug-and-play third party integrations and web hooks, profile pictures, voice/video chat, screen sharing, or any number of a plethora of other features that BOTH Slack and Discord have.

If you want people to use an open source alternative to Slack or Discord, then people need to build that alternative. IRC, unfortunately, is not it (at least not in its current aged state).

Re: Please don't use Slack for FOSS projects (2015)

#14
My only issue with IRC as the alternative to Slack is that its really user hostile. Clients largely look like some 90s programmer’s idea of a chat tool, and as discussed, persistence and sharing files and things are extensions or hacks on top of the protocol. Without addressing these, IRC is going to remain the ‘underground’ tool it is at the moment, with little support from enterprise tools and other integration providers.

Personally, I’m a big fan of MatterMost[0] as its also open source but provides a much more Slack-like experience which new users will be immediately familiar with. You can host it yourself and it works with lots of existing integrations.

[0] - https://mattermost.com/

Re: Please don't use Slack for FOSS projects (2015)

#15
post #8
post #6

Earlier quoted context omitted.

Doesn't IRC support the registration of usernames?

Most servers do, and a simple channel mode solves the spam problem (which isn't nowhere near as much of a problem as email spam).

I don't believe that it does. For a week or two about a year ago, freenode had a problem where accounts would join channel, spam links to sites accusing prominent people of child porn, and be kicked a moment later.

If there's a channel mode that can stop that, while still keeping the channel useful for people who need support, I couldn't find it.

Re: Please don't use Slack for FOSS projects (2015)

#16
post #3

Funny to see this reposted today, as just today I encountered an open source project which primarily uses Discord for chat - a terrible idea for all the same reasons. I had planned on writing a similar follow-up article reminding people that Discord is a bad communication medium for open source projects, too. I think that this is something the community ought to be occasionally reminded of, lest we lapse.

Is mumble[1] a decent replacement for discord? I like the idea of the immediacy of voice chat for talking over ideas and issues.

[1]: https://www.mumble.info/

Re: Please don't use Slack for FOSS projects (2015)

#17
post #8

Earlier quoted context omitted.

Most servers do, and a simple channel mode solves the spam problem (which isn't nowhere near as much of a problem as email spam).

I don't believe that it does. For a week or two about a year ago, freenode had a problem where accounts would join channel, spam links to sites accusing prominent people of child porn, and be kicked a moment later. If there's a channel mode that can stop that, while still keeping the channel useful for people who need support, I couldn't find it.

Freenode channels can require users to be registered and identified in order to join. This solves the spam problem. Given that I am on Freenode 24/7 and have been for years, on 40+ channels, and spam has never been an issue I stand by my original comment.

Re: Please don't use Slack for FOSS projects (2015)

#19
post #16
post #3

Funny to see this reposted today, as just today I encountered an open source project which primarily uses Discord for chat - a terrible idea for all the same reasons. I had planned on writing a similar follow-up article reminding people that Discord is a bad communication medium for open source projects, too. I think that this is something the community ought to be occasionally reminded of, lest we lapse.

Is mumble[1] a decent replacement for discord? I like the idea of the immediacy of voice chat for talking over ideas and issues. [1]: https://www.mumble.info/

I think so, yes. I also use Jitsi for pre-arranged video/audio chats, as opposed to persistent audio chat channels like Mumble offers.

Re: Please don't use Slack for FOSS projects (2015)

#20
As much as I dislike using a proprietary chat app, Discord is well designed and easy to use. Reliving the early internet is great and all but my time is limited, and I'm sick of sacrificing my time and sanity faffing around with bouncers and garbage IRC clients. It's the same reason I use macOS instead of Linux. I don't just want a Unix environment, I want a polished Unix environment where apps don't have Linux UI syndrome and plugging in an external monitor doesn't require me to pull up the man page for xrandr. That's a sacrifice I'm willing to make.
Post reply on HN