61–70 of 840 posts
Earlier quoted context omitted.
To be fair, IRC doesn't do a lot of things Slack does. Where is the logging and audit trails, access control, search, etc.
I'm still dreaming of a world where everyone uses IRC through an interface identical to Slack or Discord or whatever, and features like these are implemented.
These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.
To be fair, IRC doesn't do a lot of things Slack does. Where is the logging and audit trails, access control, search, etc.
Only centralized history/logging and search would need to be bolted on if needed. In the non-centralized case your IRC client takes care of all of that.
Maybe we can chat with coworkers here. Is there a Carl around?
Seems to be working intermittently, however.
Earlier quoted context omitted.
To be fair, IRC doesn't do a lot of things Slack does. Where is the logging and audit trails, access control, search, etc.
I'm still dreaming of a world where everyone uses IRC through an interface identical to Slack or Discord or whatever, and features like these are implemented.
Could it be the obvious? Everyone signing on / loading slack clients at the same time?
Earlier quoted context omitted.
I'm still dreaming of a world where everyone uses IRC through an interface identical to Slack or Discord or whatever, and features like these are implemented.
You might appreciate matrix.org / element.io if you haven’t seen them yet
https://battlepenguin.com/tech/matrix-one-chat-protocol-to-r...
It works fairly well.
These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.
How many more outages until all trust is eroded and competing services differentiate themselves on the basis of uptime?
I say this every time Slack is down, but they just seem so shady to me. Nobody can connect right now, and their status site says "100% uptime in the last quarter". Maybe it's close to 100%, but it ain't 100%. I think we should push for a metric where "up" means 100% of people that want to use the service are able to use the service. If 1% of users can't send messages, then that should count as a full-blown outage and…
I was wondering why the link from a Jira wasn't opening in slack, the page eventually timed out and gave me a link to status.slack.com where it told me everything was peachy. Cue me wasting time trying it again because apparently there was no issue with slack..