News for hackers. Stuff that matters.
Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:10PM (#11878540)
The question I have is why aren't industry leaders contributing to these specs? Why isn't Slack sending RFCs to improve IRC?
Re:Slack Connectivity Issues by skywhopper on Friday June 10, 2016 @02:14PM (#11878583)
What benefit would it be to Slack to publish their protocols? Or to IRC to know about them? I think the chances are extremely slim that IRC could be improved by knowing how Slack works. Slack is not a technical marvel with mysterious underpinnings. It's a centralized chat service with a pretty interface, simple clients, and (the secret sauce that won them all the converts) seamless integrations with pretty much every other open or semi-open service out there.
Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:38PM (#11878805)
IRC would benefit simply by having someone that's actually working to improve it. It doesn't matter if the improvements are superficial; humans are superficial, that stuff matter a lot.
Re:Slack Connectivity Issues by api on Friday June 10, 2016 @02:13PM (#11878563)
There is no economic model to support free/open systems and standards. It's in nobody's best interest.
Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:36PM (#11878778)
Slack's business is built on free/open standards, they don't exist without http and html. Asking them to contribute in their area of expertise is not asking a lot.
Re:Slack Connectivity Issues by ams6110 on Friday June 10, 2016 @02:48PM (#11878895)
Not just that, none of the current web economy exists without linux and gnu and other free/libre software.
Re:Slack Connectivity Issues by aaronbrethorst on Friday June 10, 2016 @02:11PM (#11878547)
Why would they want to? Improving IRC does nothing to benefit Slack.