This is becoming so often it's embarrassing really. The way it's handled in the app is also not ideal to say the least - only indication that something is wrong is that the text you are trying to send is greyed out.
[deleted]
Slack was down
161–170 of 243 posts
Re: Slack was down
#162If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.
It seems appropriate to also mention https://mattermost.com/ as a valid Open Source alternative to Slack.
We use this at work alongside Gitlab.
Works perfectly.
'Bot' scripts can also be added to do things like tell a channel when a repo has been pushed etc. Very handy.
Re: Slack was down
#163Earlier quoted context omitted.
So, what you're saying is there's tons of technologies lying around that are a solid UI and some extra features away from being valuable to normal people. But somehow doing those things and making lots of money is bad?
No, of course not. Neither adding some minor extra features (that make a huge difference for the end-user) nor profiting from it is bad. My concern was that there is so much good tech that is not being utilized just because it lacks enterprisey look and marketing attention. Take slack as an example: ircd with logging enabled + elastic search/sphinx/lucene + web frontend (use any existing web irc client and integrate…
> ircd with logging enabled + elastic search/sphinx/lucene + web frontend
Slack is way more than that, though.
My recollection is that even the initial version of Slack was more than that.
At this point, it's enough that "let's extend ircd" isn't exactly a practical answer. Either they maintain their own incompatible fork of ircd or they try to force their business desires into the irc protocol.
There's plenty of things that are "just X plus some paint" if you don't look at them deeply. That usually does an extreme disservice to the difficulty of the "plus some paint" part, and often represents a failure to understand the features involved.
Re: Slack was down
#164There are a lot of such issues recently on many major websites/services. Is it just me or are those more frequent than a few years ago?
Absolutely feels like that, if it's true would be a task for DownDetector or similar sites with their datasets.
However, this may be the result of increased dependence on centralized services which gain more and more traffic, which is more difficult to handle and even simple Regex rules (see Cloudflare outage recently) can break everything. To be honest, I don't want to ever be in charge of keeping such complex systems online.
Re: Slack was down
#165Since we have GSuite at work, figured I'd post my first thread to chat.google.com and imagine that's our plan for #SlackDown. Don't imagine anyone will notice and that life will carry-on. Even created #general ;-)
It's a really viable fallback - I did the same thing this morning. The only difference is the team / channel aspect. While Google Chat supports those features, the effort to seamlessly fallover to "backup channels" is harder than DM-type stuff.
Re: Slack was down
#166If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.
> then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I really want to like Zulip Chat. It has everything all the alternatives have + self-hosting, but as soon as they switched to their Electron client, it has become yet another resource hog that I have to put up with. I already have to put up with 10+ electron apps slowing down my Macbook. I shouldn't have to make s…
Zulip desktop is working to move from a electron's webview to Browserview. Slack has completed that migration and seems to have received a good control on its memory usage after that. Hopefully, once Zulip migrates it stops being a resource hog.
Re: Slack was down
#167Earlier quoted context omitted.
They actually just fixed that in 4.0: https://slackhq.com/introducing-a-more-efficient-slack-deskt... I'm currently sitting at 400MB total usage (including helpers) for 4 workspaces.
Half a gig for IRC + gifs
If we dont support the bloat wear created from silicon valley what will those javascript devs do. All the barista jobs are taken.
Re: Slack was down
#168Earlier quoted context omitted.
They actually just fixed that in 4.0: https://slackhq.com/introducing-a-more-efficient-slack-deskt... I'm currently sitting at 400MB total usage (including helpers) for 4 workspaces.
400MB for what basically is a client for a proprietary version of IRC is ridiculous. How much memory did BitchX use ?
I have irssi reporting 25232 mem used
Re: Slack was down
#169Earlier quoted context omitted.
But... we pay managed solutions like Slack so we have 100% uptime...
You pay for "close" to it, but no chat app is going to have 100% uptime at scale.
A frequent use case seems to be internal chat for medium size companies. I’d wager that for a majority of the user base it doesn’t need to work ”at scale”. Hopefully, outages like this will serve as a reminder.
Re: Slack was down
#170Earlier quoted context omitted.
I don't think this is the appropriate forum for "is down" postings. Post-mortems are interesting.
And yet it is the first place I checked to verify my experience
I suggest https://downforeveryoneorjustme.com/, slack its own self, or https://www.isitdownrightnow.com/ or https://hosting.review/check-if-website-is-down/ or https://www.isitwp.com/uptime-checker/. No need to fill this site with three or four postings with non-substantial comments.