Live data from Hacker News

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

news.ycombinator.com

571–580 of 624 posts

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

#571
Does anyone actually prefer coding to the IRC and XMPP protocols instead of the Slack API ?

https://github.com/erroneousboat/slack-term seems more than sufficient to me, and hackable if I find an itch to scratch...

Better yet, would anyone here pay for development of a self-hosted IRC or XMPP gateway to Slack? :P

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

#572
post #343
post #267

Earlier quoted context omitted.

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 re…

All good points there, and agreed about automated testing, I think the most you can hope for in that department is linting level testing (color contrast, valid html, associated labels and form controls, etc.)

The hard things like focus control require manual testing, ideally by a skilled user of AT.

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

#574

Earlier quoted context omitted.

Discord's inability to separate identities is the deal breaker. I don't want to be logged into work and play at the same time. I'd also like to be able to engage in some communities pseudonymously and others not. None of the chat apps ticks all boxes, which is why we need a universal client that puts the user back in control like in the Trillian/Adium days. And no, matrix+bridges is not that solution.

What's the problem with matrix plus bridges? I am uniformed, so don't take this question to imply there are no problems

As someone also relatively uninformed, when my team moved to Slack I was hoping to get a Matrix integration going. But I don't have admin rights to install the needed integrations on the slack side (and I think we're at max integrations anyway, somehow, why is that a thing...). Though recently I found a different type of slack-matrix bridge that works via user-puppeting, https://github.com/matrix-hacks/matrix-puppet-slack so no action needed on the slack end. Unfortunately it requires you to setup your own homeserver... One day I'd like to have a one-client solution to all these things again like I used to with Trillain/Pidgin. Matrix gets me a lot of the way there and with a little more effort (like my own homeserver) possibly all the way there.

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

#576
post #21

Earlier quoted context omitted.

They're not basically electron apps. they _are_ electron apps. And it's completely absurd that mine is currently using 1514MB of memory. If I weren't required to use Slack on a day-to-day basis, I absolutely wouldn't solely on principle.

Weird, my slack app on windows is currently using 54MB.

[deleted]

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

#577

Earlier quoted context omitted.

The desktop app allows them to Mark the checkbox of having a "native" app when selling ... And in my environment quite a few folks prefer the election app over the browser. I don't know why, though.

I prefer a dedicate app because I can alt-tab through a relatively limited number of apps compared to the dozens of tabs I may have open. For example, the desktop app will show notification count in the dock. Imagine if all of your apps had a browser version and you could always pick between a tabbed version vs standalone version. To use the tabbed version of everything would be like using an AOL app back in those da…

I simply have it in a browser window in a specific part on my desktop which I manage via i3wm. But, well, everybody has their preferences.

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

#578
post #21

Earlier quoted context omitted.

They're not basically electron apps. they _are_ electron apps. And it's completely absurd that mine is currently using 1514MB of memory. If I weren't required to use Slack on a day-to-day basis, I absolutely wouldn't solely on principle.

Weird, my slack app on windows is currently using 54MB.

[deleted]

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

#579

Earlier quoted context omitted.

This is pretty good explanation. https://media.8ch.net/file_dl/25ece2fb253fc4e6cdd3ac4ed99e4f...

A file download is a pretty big commitment for an "explanation". I'm going to pass on that. :/

What browser do you use that can't play webm?

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

#580

Has anybody here switched to mattermost? How has your experience been so far? Any "gotchas" or unanticipated pain-points to be aware of?

My org uses mattermost - a logical addition since we were already heavily invested in gitlab.

I don't run the services personally but I know the guys who do, and from what I can tell it mostly Just Works. We use our org's SSO for gitlab, and we use use gitlab auth for mattermost, and all the pieces work together well.

I don't use IRC with mattermost, but there are bridges available.

Post reply on HN