Are there any decent terminal-based Slack clients? (at least until Slack decides to shut down their API...)
Tell HN: Slack decides to close down IRC and XMPP gateways
191–200 of 624 posts
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#192Is there a specific list of IRC's deficiencies somewhere? Could we start on an IETF draft to address some of those rather than throw our hands in the air and build yet another walled garden?
Well for starters IRC doesn't let you keep your hands warm when somebody posts a giphy and your system resource usage goes up to crypto mining levels.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#193Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#194Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#195I'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…
> Here's a thought: how about you write a native app for each platform? I can guarantee that the hundreds, if not thousands, of engineers working on AppKit and Windows APIs are a lot better at getting this to work than your team. Not just that, but it took them months to implement some (mind you, still not all) features that are useful for blind users that someone already did in a userscript in a few days. So yeah, I…
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#196Earlier quoted context omitted.
I have run my own homeserver, you're right it's not simple. However, the main Matrix homeserver has those bridges set up (so if you don't mind using it, you can). But in the context of a corporate environemnt, you have people who are paid to maintain services like this.
Can I bridge my Slack to the main Matrix homeserver ( matrix.org )
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#197Earlier quoted context omitted.
Why is it a bad idea? And I doubt _any_ business has centralized their communications with Slack. I’m sure they are still using phones, and email and face to face communication.
> I’m sure they are still using phones, and email and face to face communication. Slack's rise continues to baffle me. It's not good or widespread enough to replace email, Skype messenging, SMS or phone calls - so it's yet another thing I have to stay on top of at work. My life would honestly be easier without Slack.
Baffling that so many people still use it as yet another mode of transportation.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#198Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#199Slack 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…
You just described the Matrix riot client: * https://matrix.org/ * https://riot.im/
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#200Earlier quoted context omitted.
assuming this claim is valid, that it took "few days" to implement what took them "months", then they could rewrite the entire user script from scratch every time a change is made, and this could be repeated dozens of times , which, assuming major UI changes are made once every few months, would take several years.
But, but, but, then I'd have to touch the same code twice... /s There is definitely a poison in our profession, I definitely have to fight the urge to make sure no future changes will break something, instead of just budgeting time to fix breaking changes later. Especially since no one seems to remember when we all agree something doesn't need to be bullet proof. Just today there was an expression of disbelief when I…
The difference is that they don't work in the same office as Slack. They'll never hear about all the important, completely justified reasons Slack decided to release a bad UI. They'll just notice it happened, and conclude that Slack must hire incompetent UI developers who didn't realize it was bad. Any product with a large customer base has to be pathologically averse to things like this.