Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 624 posts

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

#21

Post by castis »

zitterbewegung wrote: post #14
saagarjha wrote: post #11

I'm very disappointed to see that Slack has decided to go the way of every other messaging service and move away from decentralized and standardized protocols towards those that are walled and proprietary. > We are focused on making Slack accessible to all people. Over the past year, we've made great progress in improving both the keyboard and screen reading experiences in Slack. We know many users have been relying…

I run Slack in a browser tab . Their native apps are basically electron tabs. I wonder how many people used xmpp and irc gateways in relation to all of their active users ?

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.

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

#22

Post by duncan_bayne »

cortesoft wrote: post #5

I wonder how hard it would be to write a custom bridge with the real time api, to make your own IRC gateway?

I was thinking about this too, then I realised I'd be spending some of my own precious life helping Slack mitigate the consequences of a user-hostile, and Open Web-hostile, decisions. Screw that.

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

#23

Post by drdaeman »

Okay, I get that IRC isn't able to convey lots of modern fancy stuff, but XMPP? Really? I swear, it can do almost anything that fits into stanza exchange logic, as long as one's not afraid of adding an XML namespace (of course, it's being nice to search for already existing XEPs first). Afterwards it's client developers' problem to support shared threaded animated gif sticker emoji reactions or whatever.

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

#24

Post by saagarjha »

zitterbewegung wrote: post #14
saagarjha wrote: post #11

I'm very disappointed to see that Slack has decided to go the way of every other messaging service and move away from decentralized and standardized protocols towards those that are walled and proprietary. > We are focused on making Slack accessible to all people. Over the past year, we've made great progress in improving both the keyboard and screen reading experiences in Slack. We know many users have been relying…

I run Slack in a browser tab . Their native apps are basically electron tabs. I wonder how many people used xmpp and irc gateways in relation to all of their active users ?

Only Slack can answer that, but considering that Slack is commonly used at many technology companies I'd say that the number is probably reasonably high. I tend to find that software developers tend to have a much lower tolerance for non-native/poorly optimized/proprietary software than most people.

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

#26

Post by saagarjha »

lol768 wrote: post #19

This is disappointing. Why isn't there a public blog post about this? Why is the "more information" page behind an auth wall?

If you were Slack, would you post a blog post about this? It's clearly a negative, so there's no point in drawing attention to it.

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

#27

Post by matthewmacleod »

cortesoft wrote: post #5

I wonder how hard it would be to write a custom bridge with the real time api, to make your own IRC gateway?

Pretty easy, I reckon. I started writing a native Mac client using the API, and it was pretty straightforward. I don’t see there being a huge barrier to implementing a gateway.

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

#28

Post by ztoben »

castis wrote: post #21
zitterbewegung wrote: post #14

Earlier quoted context omitted.

I run Slack in a browser tab . Their native apps are basically electron tabs. I wonder how many people used xmpp and irc gateways in relation to all of their active users ?

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.

That's absurd. How is it so high? Mine uses around 700MB pretty consistently.

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

#29

Post by xab9 »

zitterbewegung wrote: post #14
saagarjha wrote: post #11

I'm very disappointed to see that Slack has decided to go the way of every other messaging service and move away from decentralized and standardized protocols towards those that are walled and proprietary. > We are focused on making Slack accessible to all people. Over the past year, we've made great progress in improving both the keyboard and screen reading experiences in Slack. We know many users have been relying…

I run Slack in a browser tab . Their native apps are basically electron tabs. I wonder how many people used xmpp and irc gateways in relation to all of their active users ?

I run it in a dedicated browser with one tab only (srware iron). Memory usage: 200mb. Electron crap memory usage is usually 2gb+.

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

#30

Post by cortesoft »

duncan_bayne wrote: post #22
cortesoft wrote: post #5

I wonder how hard it would be to write a custom bridge with the real time api, to make your own IRC gateway?

I was thinking about this too, then I realised I'd be spending some of my own precious life helping Slack mitigate the consequences of a user-hostile, and Open Web-hostile, decisions. Screw that.

Looks like it has already been done, thankfully :D

https://github.com/wee-slack/wee-slack

Post reply on HN