111–120 of 131 posts
Why CPU goes like crazy every time slack loses connectivity? You can easily test this by disconnecting from wifi. As soon as you're offline the fan starts spinning until you get your connection back.
Reminder why your status page should be hosted in a very different way than your regular infrastructure... so you're way less likely to end up with issues on both at the same time. I like how statuspage.io even has metastatuspage.com in case their primary domain/DNS/TLD has issues.
Reminder that you should check things first before commenting. Slack's status page is in a different infrastructure, somewhere using digital ocean while slack.com is using AWS.
Earlier quoted context omitted.
Pretty sure they provide an IRC interface, but almost certainly don't use IRC internally. There's almost no way they could support any of their fancier features using IRC. Reactions etc would be horrible to implement.
Yeah and the IRC interface has been getting worse recently. When they added the shared channels across teams they completely broke being able to '@' a user from the IRC gateway. Support said something along the lines of 'yup and we're not planning on fixing it'. I'm expecting them to completely turn off the IRC gateway in the next year or two.
Wow, talk about realising how much we rely on Slack.. suddenly I feel so disconnected and alone. https://www.customd.com/articles/65/slack-is-down
This is probably preaching to the choir, but hosting your own FOSS chat is nowadays a very viable way to avoid being dependent on a centralised service like Slack. Your options include: * Riot.im / Matrix.org (decentralised global network; e2e encryption; open protocol) * Rocket.Chat (Meteor-based; focus on UX and feature) * MatterMost.com (clone of Slack UI; open core license) * Zulip.org (all about threads!) * ...o…
Do these solutions have good mobile frontends?
So I guess yes :)
This is probably preaching to the choir, but hosting your own FOSS chat is nowadays a very viable way to avoid being dependent on a centralised service like Slack. Your options include: * Riot.im / Matrix.org (decentralised global network; e2e encryption; open protocol) * Rocket.Chat (Meteor-based; focus on UX and feature) * MatterMost.com (clone of Slack UI; open core license) * Zulip.org (all about threads!) * ...o…
Is there reason to believe self hosting will have better uptime?
Here at FB, a lot of day to day coordination takes place via FB products. But production and release engineering communication happens over IRC, especially during major outages. The fallback factor in critical to keeping the plane in the air.
I've switched to using TwistApp ( https://www.twistapp.com ) with my team. Unlike Slack where you have channels where everyone talks about everything, TwistApp bases conversations around threads. Every problem that's being worked on has its own thread. Once it's completed, I close and archive the threads. Very effective for getting things done as every task is isolated in a separate thread and discussions don't overl…
Earlier quoted context omitted.
Perhaps the HN mods should do something about that then.
If you see something like this and you think it's in error, you can let them know and they'll likely be able to respond more quickly. There's a contact link in the footer.
Earlier quoted context omitted.
If you see something like this and you think it's in error, you can let them know and they'll likely be able to respond more quickly. There's a contact link in the footer.
You're joking, right?