Not even for companies, IRC IMO would be much better, the only issue is, as always, you need someone responsible for the infrastructure: ...
Not even for companies, IRC IMO would be much better, the only issue is, as always, you need someone responsible for the infrastructure: not only servers, but scripting for Jira/Dropbox/NameYourCurrentTrendyPlatform integration. -No single point of failure. -No dependency on a different company for a vital points of your business. -No private info stored on a 3rd party system, in a different state and potentially a different country (legal nightmare to ask for damages). -Distributed system. Local servers give lower lag for multisite companies, internet access outage means netsplit, not inability to communicate. -Already existing indexing and searching features if desired. -Many bots to automate/notify/interact with insane amounts of stuff. -Thousands of IRC clients, with enormous customizing features, for every conceivable platform, that do as much and even more than all these "this is how communication should be" solutions. -Bridging IRC to XMPP/Sametime/etc plugins/apps to interoperate with other companies. I can sort of understand Slack for a small company, but if you have your own server infrastructure, no, I can't.
Posted by Uberphallus on Mar 25, 2015, 9:07 AM
Tags
Related issues
- I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
- [BUG] No response from API error when Advisor is triggered
- I thought the general premise is that humans can't form social groups bigger than around ~200.
- great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
- > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
- Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
reliability (Network)
I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
[BUG] No response from API error when Advisor is triggered
I thought the general premise is that humans can't form social groups bigger than around ~200.
great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
> It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Copy and paste not working
Full Offline Support
Not even for companies, IRC IMO would be much better, the only issue is, as always, you need someone responsible for the infrastructure: ...
Not even for companies, IRC IMO would be much better, the only issue is, as always, you need someone responsible for the infrastructure: not only servers, but scripting for Jira/Dropbox/NameYourCurrentTrendyPlatform integration. -No single point of failure. -No dependency on a different company for a vital points of your business. -No private info stored on a 3rd party system, in a different state and potentially a different country (legal nightmare to ask for damages). -Distributed system. Local servers give lower lag for multisite companies, internet access outage means netsplit, not inability to communicate. -Already existing indexing and searching features if desired. -Many bots to automate/notify/interact with insane amounts of stuff. -Thousands of IRC clients, with enormous customizing features, for every conceivable platform, that do as much and even more than all these "this is how communication should be" solutions. -Bridging IRC to XMPP/Sametime/etc plugins/apps to interoperate with other companies. I can sort of understand Slack for a small company, but if you have your own server infrastructure, no, I can't.
Comments (0)
No comments yet. Start the discussion.