Live data from Hacker News

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

news.ycombinator.com

341–350 of 624 posts

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

#341

Earlier quoted context omitted.

Free for some providers that have Sameroom-operated "BridgeBots". Any combination of Hangouts, Skype, GroupMe, Telegram, and Gitter is free to connect. We also had a Freenode BridgeBot, but couldn't get around the max connections per user issue.

Does that mean if I want to use an open source client with Slack, I can use the Gitter BridgeBot and open source Gitter client? Does it work with private Slack channels?

It does

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

#342

Earlier quoted context omitted.

So much this! I happen to be a blind software developer who has had just this sort of experience in years gone by. Web apps mean that you are at the mercy of the developers. Something can work one day and break the next. This is even more true for blind people than it is for the general public. Even if there is accessibility testing, I doubt that it covers my particular toolstack. I'm on Linux. So I'm doubly a niche…

Just curious — how do you effectively program blind? Seems to me like a really difficult problem because coding is about jumping around so quickly and needing to be able to scroll and grok at high speeds. You also have the issue of all kinds of specialized characters that are difficult for any kind of text-to-speech. Are there specialized Braille displays for this kind of stuff? How do you go back and forth between k…

Since you mentioned braille displays, some blind programmers do use those. They're expensive though ($1000 or more). Computer braille has 8 dots per cell rather than 6. That's a good fit for ASCII.

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

#343
post #267

Earlier quoted context omitted.

So much this! I happen to be a blind software developer who has had just this sort of experience in years gone by. Web apps mean that you are at the mercy of the developers. Something can work one day and break the next. This is even more true for blind people than it is for the general public. Even if there is accessibility testing, I doubt that it covers my particular toolstack. I'm on Linux. So I'm doubly a niche…

Besides building accessibility into frontend/React component toolkits, how do we automate testing for accessibility? I've turned on text dictation and tested apps with a blindfold, but that doesn't scale and I'm not even sure if it's how people really use an app without sight.

After years of trying, I've still not found a reliable way to automate accessibility testing. The only really workable way to manage it currently is: bake it into your entire dev process.

When designing an application, forget the visuals: design the flow of information, and the interactions. This is a surprisingly good facsimile for mobile-first thinking, as it follows similar principles: in both cases, you have a restricted amount of information to display, and have to design to deal with that.

Once you've got the information flow, step from there to visual elements, and ensure that as you build, you're baking in ARIA support and your testers are interacting with it using VoiceOver/JAWS.

At the end, the fact is you won't have anything perfect, but you'll have something better than the majority of sites out there. The reality is that perfection is impossible, but if you bake inclusive thinking into your app from the get-go, it's pretty straightforward, and you usually end up with an application that is less confusing and overloaded with information for your visual users too.

If you leave it as something to slap on at the end, it's almost always impossible.

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

#345

> After years of evolving, Slack is at the point where the gateways can no longer handle all of our features or security needs. I don't think Slack ever cared much about the gateways. I have used the IRC gateway for years, and it was never compliant with IRC protocols. I even had to patch my IRC client to work with Slack. IRC is also being extended with new features [1], some of which are designed specifically for ga…

I attempted to use the xmpp gateway for a while before realizing it had a bug which caused the gateway to spam messages on reconnection. I contacted support and they said it was an intended feature and they wouldn't support proper xmpp group standards. That was the day I ditched slack forever.

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

#348
post #337

Earlier quoted context omitted.

Not the OP and not blind, but I've worked with a blind programmer before. You move your cursor in the code and it reads you the line. The screen readers can be adjusted so that the speed of reading is really fast. To someone who is not used to it, it sounds like gibberish. But it's pretty amazing how fast the speech can be. After that, it depends on the editor. My colleague used vi (this is a long time ago -- before…

> You move your cursor in the code and it reads you the line. That's somewhat similar to how ed works. You choose a line number or range and print those lines to the screen.

Since you mentioned ed, I know of a blind programmer who actually likes and uses ed (or did last time I heard from him). In fact, he wrote his own version of ed that also includes a web browser, and called it edbrowse. To be sure, he's in the minority even among blind programmers. But for what it's worth, you can find an article that he wrote about his approach here: http://www.eklhad.net/philosophy.html
Post reply on HN