531–540 of 624 posts
Earlier quoted context omitted.
The ~600 person distributed company I work for doesn't use phone or email and obviously doesn't do anything face to face. We relied on IRC for years before switching to Slack so yes, all of our real-time communication is via Slack. We have internal blogs for threaded important async discussion though, but Slack is where our high bandwidth talk done.
How come you don't use Rocket.Chat or Mattermost or Matrix?
Great, I feel like an idiot. I advocated slack, because it granted the freedom to choose a client. Now I helped lock-in others. Suggestions for alternatives, that I could migrate to? The requirements are: mid sized teams, desktop and mobile, all major os. People used web based client, native clients, irc gw, and bots. We need search and archive. Self-hosting is an option.
Earlier quoted context omitted.
Why would one want to use Relay instead of Mattermost?
Relay is actually hosted mattermost. Just a means to offload maintenance and uptime to someone working on it full time. The part of software in Relay that makes mattermost SaSS is open source too.
Earlier quoted context omitted.
Maybe we could do something about voicemail then? ducks
What do you mean? Voicemail was never successful and the reason is simple: verba volant, scripta manent , spoken flies, written remains.
Earlier quoted context omitted.
As someone who doesn't use slack, why did we ever move away from chat programs and protocols that worked fine? I don't know why I need to use slack, hangouts, discord, etc, that are just reinventing irc and/or the garden variety instant messaging platforms that already exist.
I don't know why I need to use slack [...] just reinventing irc Features Slack has that IRC doesn't include: * User authentication * Support for multiple concurrent logins by one user * Persistent, searchable history * (Ad-free) file and image sharing built in * Simple integrations, like webhooks, built in. In other words, Slack is like IRC+NickServ+Irssi+Screen+Imgur, except easier to use, in the sense that you don'…
It's closer to Slack is like DALnet.
That said, this is a money grubbing exercise that isn't justified by any technical means.
Earlier quoted context omitted.
JAWS is Windows-only, so your solution of just targeting JAWS is not a solution at all, since Slack runs on a lot more platforms.
Accessible users are primarily on windows because JAWS runs on windows . It is not a use case for us to test accessibility on anything other than JAWS on windows.
Earlier quoted context omitted.
Turn message forwarding off and nothing will happen, I've lent my cell # to broke friends afew times to make a Google Voice account, and have a Voice number myself for Craigslist exchanges, lapses between paying my carrier, etc
you seem to miss the point. 1) get US phone 2) register google voice to US phone 3) stop paying for US phone 4) you can't de-register you US phone, unless you register a new one 5a) if you never sign up for a US phone, anybody can get assigned that number and click "forgot password" on your google voice. 5b) you get a new US phone: go to 2. that is true for every single service that ties you up to a phone number or t…
Earlier quoted context omitted.
> Slack initially integrated with IRC and XMPP because they were more popular than Slack. Bait > Now that Slack is much bigger than all IRC and XMPP traffic combined, the integration is no longer worth its weight in code. Switch
sorry, but i don't agree. this is a classic EEE i.e. Embrace, Extend, Extinguish maneuver. which is what, afaik, the gp was trying to say. edit-001: fmt changes.