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

441–450 of 624 posts

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

#441

Post by lorenzhs »

MaxLeiter wrote: post #66
nopacience wrote: post #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…

A few projects exist that try to be "modern" UIs for IRC (bias: I contribute to Lounge) TheLounge - https://thelounge.chat (FOSS, self-hosted) IRCCloud - https://irccloud.com (mobile clients OS, hosted)

Let me add Glowing Bear, a project I contribute to that builds on top of WeeChat: https://github.com/glowing-bear/glowing-bear

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

#442

Post by aerique »

spdionis wrote: post #421
flukus wrote: post #381

Earlier quoted context omitted.

Interesting, how do blind developers feel about minimalist languages like lisp? On one hand it seems like it would read very well in some circumstances (+ 1 2), but the scoping could be a real pain. Cobol seems like another language that might be well suited to them.

"parens parens parens parens parens parens parens some code here parens parens parens"

Ugh, that won't do. I need my: brace bracket paren asterisk some code paren bracket brace semicolon.

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

#444

Post by lolikoisuru »

azangru wrote: post #228
ocdtrekkie wrote: post #146

Earlier quoted context omitted.

Discord has all the same problems Slack does. It's a proprietary VC-funded app without a sustainable business model.

What's Discord’s business model? Slack has a paid-for tier, but I haven’t seen anything like that on Discord.

This is pretty good explanation.

https://media.8ch.net/file_dl/25ece2fb253fc4e6cdd3ac4ed99e4f...

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

#445

Post by abhin4v »

nqzero wrote: post #379
ankitank wrote: post #370

Earlier quoted context omitted.

Go host your own messaging tool: Relay is an alternative to slack. Relay is open source, built on top of Mattermost. This means you can host Relay yourself. https://relay-chat.com/

i see the comparison to slack, but how does it compare to mattermost ?

Relay is built on Mattermost team edition so it has all the team edition features. It plans to add new features as per user feedback which will be contributed upstream to Mattermost.

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

#446

Post by agroot12 »

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…

I think it would be much better if the screen reader could use sounds for punctuation, like the sound of a typewriter typing to indicate a dot, and some meep-like sound with the frequency goes up for an opening parenthesis, and down for a closing parenthesis.

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

#447

Post by aestetix »

It seems that there is an increasing trend from Bay Area tech companies (maybe tech in general) to bootstrap by taking in users feedback (twitter RT feature), get to a certain size, and then totally abandon their base.

To an extent this makes sense, like if there is a new company CEO who has a different vision, etc. But many of these decisions-- dropping Google Reader, the trend to ditch the headphone jack, and now Slack killing IRC-- seem to be made for no apparent logic reason, and giving some bullshit excuse like "security reasons."

Is this driven by data? If so, why don't they release the data and show us? Alternatively, in a free market, the way to best compete is to offer more options to your customers, unless you've attained a semi-monopoly, or have some kind of trust agreement.

Is it that difficult to maintain these things? Apple and Google are among the richest companies in the world, and Slack just raised $250 million. Given that not only are all three features I'm discussing established and probably only need occasional maintenance, the headphone jack has been around for over 100 years. It's not like they need new science breakthroughts for it.

None of it makes any sense, unless the entire Bay Area has gone Dilbert.

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

#448

Post by mixedmath »

Kudos wrote: post #188
nopacience wrote: post #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…

The two things IRC is actually missing for most people is push notifications and "offline" history. Yes you can get these if you run your own bouncer, or whatever, but it's not native to the technology. I think Matrix is ahead of IRC for solving both of those issues.

IRC is the protocol. There are myriad services which use the IRC protocol. Some of these do include push notifications and offline history, such as irccloud (and others).

The freedom to choose is one of the reasons people wish slack would open source their protocol.

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

#450

Post by aepiepaey »

rocky1138 wrote: post #257
seangrogg wrote: post #168

Mmm, while this wouldn't have impacted my decision in the slightest, I am mostly glad that I have moved over to Discord for everything I used to do in Slack.

Is Discord any better? It's still a centralized service run by one company, is it not?

Can't speak for Slack, but Discord is a fully walled garden, and they make sure to control how content on the platform is consumed.

You can't automate your own account in any way without risking a ban due to breach of ToS (see "self-bots").

This makes it impossible, for example, to get local chat logs (as the official client doesn't support it).

Post reply on HN