Live data from Hacker News

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

news.ycombinator.com

31–40 of 624 posts

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

#31
post #21

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.

GP said "basically electron tabs", as in the electron wrapper is functionally equivalent to a browser tab.

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

#32
Slack was fine, now it is time to move back to IRC.

Some people like slack or telegram because they provide an API for BOTs. Something IRC has been open to since the begining.

Non power users might have trouble using IRC with the usual clients (mIRC/irssi/bitchx).

Today a family member, not technical and 60+yrs asked about "that tool" that is like whatsapp however it allows users that just joined a group to read old messages. He was referring to slack. He wanted to create a group and when new users from his company joined, they would be able to read whatever was written on that group.

So with this in mind, i think what would really work (also) is to have something on the front of IRC (some bouncer) with a pretty UI that logs everything and allows new users to connect via mobile, standard irc clients, and also send pictures, and read backlog (stuff slack does). However the backend chat server should be the decentralized existing ones, efnet/freenode/etc.

So maybe its time to re-invent slack and make a pretty UI to access usual standard IRC. ie. a new slack that uses old irc networks (decentralized networks) as its backend. But also allows users to talk from mobile apps, browsers, etc

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

#33
post #13
post #8

Of course they do. This is exactly the path Google took. Once you achieve enough power in the market, you can throw open protocols overboard. It's a symptom of the centralized world the internet has become.

Yeah, I don't want to be a downer, but this is pretty much the exact definition of Embrace, Extend, Extinguish: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Google is the new Microsoft. We all need to get comfortable with this idea, and fast.

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

#34
post #21

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.

I remember when Slack in a Chrome tab committed 3-4 GB. Sounds like they've made improvements.

Standalone client and its helpers are sitting on ~800MB committed on my install of High Sierra. Might be worth a shot.

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

#35
post #28
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.

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

Gifs, lot of gifs

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

#36
post #8

Of course they do. This is exactly the path Google took. Once you achieve enough power in the market, you can throw open protocols overboard. It's a symptom of the centralized world the internet has become.

My understanding was Google supported XMPP until a few companies including Microsoft only allowed their integrations one way and then abandoned it as they felt they were opening themselves up to being exploited rather than pushing an open standard.

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

#38
post #8

Of course they do. This is exactly the path Google took. Once you achieve enough power in the market, you can throw open protocols overboard. It's a symptom of the centralized world the internet has become.

XMPP support did very little to grow whatever power Google has in the chat market. Traffic to federated services and use of third party clients was low.

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

#40

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

One of my ex-colleague build one a while ago in less that a few days so I guess not that hard. But he is in the habit of making IRC gateway for everything he use
Post reply on HN