111–120 of 624 posts
It looks like IRCCloud has done an API based integration which is then exposed again via their own IRCv3 system: https://twitter.com/IRCCloud/status/971416931373854721
I'm very disappointed to see that Slack has decided to go the way of every other messaging service and move away from decentralized and standardized protocols towards those that are walled and proprietary. > We are focused on making Slack accessible to all people. Over the past year, we've made great progress in improving both the keyboard and screen reading experiences in Slack. We know many users have been relying…
>I'm very disappointed to see that Slack has decided to go the way of every other messaging service and move away from decentralized and standardized protocols If every major messaging service eventually does this maybe those decentralized and standardized protocols are the problem.
Relatedly, are there any 3rd party Slack apps out there? Their APIs are powerful and seem pretty complete.
From what I have seen the best solution for bridging chat protocols is a "tube" from https://sameroom.io - not free though.
I don't believe anyone's written a fully-functional XMPP connector yet though.
Everybody here is disappointed at Slack, and I like open protocols and open platforms just like everybody else, but I still have a contrarian view. Instead of blaming Slack, why not accept that the open protocols indeed suck? IRC does not specify encoding, netsplits are a common issue, file sending sucks, etc. XMPP also has file sending problems, does not play nice with mobile, is fragmented (not every client impleme…
"All of this has happened before and will happen again."
I'm completely unsurprised. The integrations were there to reduce customer risk in choosing slack. Now that slack is big enough, they don't need to do that anymore. Those integrations can only let 3rd parties into the party that slack wants all for themselves.
Shit like this is why IRC is still so popular.
Earlier quoted context omitted.
You post implies that you're officially affiliated with Slack. If so, are you really comparing yourself to "Micro[s]oft's playbook"? Why can't you work to fix the issue rather than follow the industry standard?
looks to me like they just copy/pasted the MOTD from an irc client that connected to slack's gateway
Everybody here is disappointed at Slack, and I like open protocols and open platforms just like everybody else, but I still have a contrarian view. Instead of blaming Slack, why not accept that the open protocols indeed suck? IRC does not specify encoding, netsplits are a common issue, file sending sucks, etc. XMPP also has file sending problems, does not play nice with mobile, is fragmented (not every client impleme…
Agreed. I have never had as good of an experience with IRC or XMPP as I have with slack. Open protocols are still great for open communities, internet discussion boards, etc. but when you're a multi-billion dollar messaging platform and companies are using you for critical communication I don't see any reason to continue supporting them. They've actually gone a step further and put the accessibility features in slack…
It's absolutely possible to provide all this in open protocols, and even in a reasonable timeframe.
Earlier quoted context omitted.
Animated custom emojis seem to be a common thread, animated images in general cause my CPU and memory to spike when using slack. Our network engineer loves this dancing parrot emoji but it basically pins a core on my machine and adds 20-30% of memory to slacks process. I've switched over to using mattermost, it can be (and is) self hosted so I'm not as worried about slack getting hacked (again) and leaking our info/t…
Mattermost is also an example of how not to license software, including a promise not to enforce provisions of the license they have chosen. If one needs a promise, one has probably chosen the wrong licensing structure. Here's a fun one: say I use the MIT binaries, then debug a problem by reading the AGPL source code. What legal position am I in? (If you have an answer for that rhetorical question, by the way, you ha…
Everybody here is disappointed at Slack, and I like open protocols and open platforms just like everybody else, but I still have a contrarian view. Instead of blaming Slack, why not accept that the open protocols indeed suck? IRC does not specify encoding, netsplits are a common issue, file sending sucks, etc. XMPP also has file sending problems, does not play nice with mobile, is fragmented (not every client impleme…
But, I've never used Slack nor would use it as I'm biased towards it's prop nature, especially when it's used (and even promoted) within open source communities.
Earlier quoted context omitted.
Not to mention that Chromium takes a performance hit when accessibility is on – that's why it's off by default. But both Safari and native Mac apps are always accessible.
Well, in this case I was quite glad that they have targeted the web platform. At least that allows me to code my own stopgap solution using userscripts and stuff. That's harder for native.