Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>It's significantly easier to get to team-based outcomes if you can adhere to a common platform.

Both the good outcomes and the bad outcomes. Cue the recent Slack WYSIWYG editor woes.

Slack used to have an IRC gateway, allowing anybody to peruse it from any OS, on any device, with any UX. The Slack corp. chose to supply UI for one popular platform (Electron), and cut off[1] any other means of access. This single platform focus did put Slack in full control of the UI and UX of the messenger, and able to force the WYSIWYG editor on all users.

Without the overwhelming dominance of one platform (Electron), Slack most probably would feel the need to maintain the fully featured IRC gateway, letting people interface with it fully via alternative means.

--

[1] the APIs are un(der?)documented, changing, and you are on your own



I use wee-slack with weechat, works great. It is definitely a better experience than when I was using the irc gateway.


Whenever I see a new IM service pop up, my first two questions are:

1. Is it FOSS?

2. Can I use it in Weechat?

That's really all that matters to me. I currently use Weechat to handle IRC and Matrix.org.

I've had to use Slack in an internship in the past. Thanks for mentioning wee-slack; I'll keep an eye on it should I be subjected to a proprietary IM service again.


irccloud.com (needs a paid account) will provide an BNC interface to a slack - been using that for a while to talk to customer slack setups, works really nicely.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: