Tell HN: Slack decides to close down IRC and XMPP gateways

Post by flukus » Thu, Mar 08, 2018, 6:46 AM UTC

mwcampbell wrote: post #331

azinman2 wrote: post #308

Earlier quoted context omitted.

But how does it sanely pronounce things with abbreviations or even something like: NSDictionary *myCompoundedWord = @{@“key: [NSNumber numberWithInt: 7] }; And know that it’s missing the terminal “ in the string and has an extra space after the ]? Seems very difficult. Would be great if it could understand the language enough to verbalize it at a higher level.

With the punctuation level set to all, the NVDA screen reader for Windows reads your code snippet like this: n s dictionary star my compounded word equals at left brace at left quote key colon [pause] left bracket n s number number with int colon [pause] 7 right brace right bracket semi It's a lot to absorb, but people do program productively this way. For example, the NVDA screen reader is itself developed primarily…

Post by e12e » Thu, Mar 08, 2018, 6:52 AM UTC

yorwba wrote: post #362

rb666 wrote: post #354

Earlier quoted context omitted.

Discord is amazing, there really isn't a good replacement right now. Before that it was a mess/mix of IRC/Skype/Teamspeak/Whatsapp, now you can combine all that in one great client from a company that actually seems to care about its users. It's my favorite monthly Paypal charge!

When I combine the feature set of IRC/Skype/Teamspeak/WhatsApp, I come up with text chat + voice/video conferencing, which e.g. Skype already provides. Is the difference that the client is great?

Post by [deleted] » Thu, Mar 08, 2018, 7:03 AM UTC

fyfy18 wrote: post #378

ndarilek wrote: post #277

Earlier quoted context omitted.

Oh man, makes me so happy to see the accessibility concerns at the top of this thread. I hate Slack so much. Nothing has made me say "is 10 AM too early for a beer?" quite so much as that absolute pile of uselessness. I thought they'd actually improved their accessibility story when my screen reader read various elements as buttons. Later I discovered that, while they'd likely added the correct ARIA role to a , they…

As a developer who should probably pay more attention to this than I do, can you recommend some reading material about how to make an app accessible, and how to make sure it stays accessible (i.e. is there a good way to CI test this?).

Post by pseudalopex » Thu, Mar 08, 2018, 7:09 AM UTC

eadmund wrote: post #244

anglebracket wrote: post #159

Earlier quoted context omitted.

I don't believe so. emacs-slack uses their official OAuth2 + Websocket integration https://github.com/yuya373/emacs-slack#how-to-get-token-the-...

This is, incidentally, an argument about how a well-designed system like emacs can make writing a truly-native app easy : so easy that some random guy was able to take the API and write a client for a text editor (granted, the greatest & best text editor the world has ever known …). If it's so hard to write native macOS, Windows, gtk+ or Qt apps — maybe that's a fault of those development environments. Granted, 'disp…

Post by einr » Thu, Mar 08, 2018, 7:16 AM UTC

Spivak wrote: post #322

dfabulich wrote: post #132

Earlier quoted context omitted.

The IRC gateway was there to mollify people who said "IRC is better! I refuse to switch!" Slack advocates could say, "Don't worry, you don't have to switch. You can just keep using your IRC client with Slack. Everybody else will have a web UI, which they prefer, and you can keep using Irssi. Everybody wins."

Right, and now that everyone is hooked the loud minority (if we're being honest with ourselves) have to choose between speaking the Slack protocol or losing access to our contacts. Are we doomed as a community to be surprised every time a company with power squeezes?