91–100 of 131 posts
Slack is currently down and I've realized, for better or worse, what Slack has really done.. It's created an expectation for immediacy. I thought about sending my question to someone via email but then just thought, "I'll wait for Slack to be back up, it'll be faster anyhow".
My first thought: "Slack is down? Better post to Slack and let the team know."
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…
When the status page is returning a 500 error... not a good sign.
On the other hand, makes it sound more likely to be a routing/reverse proxy issue instead of (say) a database issue. Those sound easier to deal with via a rollback vs something like "oops we dropped a critical index on the `messages` table".
https://aws.amazon.com/solutions/case-studies/slack/
The API isn't even returning valid error codes.
logging error: {"subtype":"api_call_error","message":"{\"ok\":false,\"error\":\"_http_error\",\"status\":0,\"retry_after\":null}","stack":"Error\n
I am betting they are saying 'connectivity' because that is the error the client logs.
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?
2. You can perform maintenance outside of office hours, with SaaS you don't get to decide when an upgrade (and potential outage) happens. I don't care about 99% uptime, I care about having 99% uptime while I'm working.
3. You can have backup services.
Also read this post by Amir, the founder of TwistApp, "Why we're betting against real time messaging" - https://blog.doist.com/why-were-betting-against-real-time-te...
Earlier quoted context omitted.
Is there reason to believe self hosting will have better uptime?
1. Self hosting doesn't have to operate at the scale of slack, so there's a whole slew of issues avoided. Pushing text messages around really isn't that difficult when you aren't serving millions of customers. 2. You can perform maintenance outside of office hours, with SaaS you don't get to decide when an upgrade (and potential outage) happens. I don't care about 99% uptime, I care about having 99% uptime while I'm…
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?
Earlier quoted context omitted.
On the other hand, makes it sound more likely to be a routing/reverse proxy issue instead of (say) a database issue. Those sound easier to deal with via a rollback vs something like "oops we dropped a critical index on the `messages` table".
With the length of the outage it seems more like a DB issue. And if this is still correct there look to be some fragile dependencies. https://aws.amazon.com/solutions/case-studies/slack/ The API isn't even returning valid error codes. logging error: {"subtype":"api_call_error","message":"{\"ok\":false,\"error\":\"_http_error\",\"status\":0,\"retry_after\":null}","stack":"Error\n As you can hit their api servers I am…
For l
They ignore:
https://standards.freedesktop.org/basedir-spec/basedir-spec-...
And kitchen sink everything under the xdg config dir...
~$ ls .config/Slack/
Cache/ Cookies-journal
dictionaries/ installation Local
Storage/
Preferences QuotaManager-journal
Cookies databases/ GPUCache/
local-settings.json logs/ QuotaManager
storage/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.