I wonder how hard it would be to write a custom bridge with the real time api, to make your own IRC gateway?
Tell HN: Slack decides to close down IRC and XMPP gateways
81–90 of 624 posts
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#82Earlier quoted context omitted.
That's absurd. How is it so high? Mine uses around 700MB pretty consistently.
Animated custom emojis seem to be a common thread, animated images in general cause my CPU and memory to spike when using slack. Our network engineer loves this dancing parrot emoji but it basically pins a core on my machine and adds 20-30% of memory to slacks process. I've switched over to using mattermost, it can be (and is) self hosted so I'm not as worried about slack getting hacked (again) and leaking our info/t…
For the curious, there's some history to that parrot emoji:
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#83I'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…
Not to mention that Chromium takes a performance hit when accessibility is on – that's why it's off by default. But both Safari and native Mac apps are always accessible.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#84Earlier quoted context omitted.
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.
That's absolutely gargantuan. How can any general purpose application justify 4G of memory, half of a factory macbook pro's memory. To put this in perspective, I was talking this week to a developer who was essentially apologising to me for a new feature that was going to require insane amounts of memory. This is for a process to handle literally millions of users. How much memory was it? 3G. Per "instance" of which…
It takes a lot of memory to slowly and jerkily send plain text over the internet, and not quite keep up with typing when autocomplete-ing usernames, you know. Stop expecting so much of your computers /s
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#85I'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'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
If every major messaging service eventually does this maybe those decentralized and standardized protocols are the problem.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#86This is super shitty.. the only reason to use slack was that you could escape from the shitty web/electron crap. Good bye slack.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#87I'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…
Most accessible users use JAWS on windows. I focus on accessibility a lot for my job. In fact, we have an entire department dedicated to accessibility design, implementation, and testing. The reason why accessible users use JAWS is that it works across the entire OS and all the programs you have installed; start menu, PowerPoint, web browser, control panel, Google, etc. etc. The problem with the native accessibility…
By tools, what do you mean exactly? The only tool you require on the OS-level is a screen reader, and it talks to the native Windows APIs depending on what application you are using. If you are referring to the different accessibility API implementations like MSAA, UIA etc. that is not something that should at all impede a native app of any kind, so what exactly are you referring to here?
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#88For weechat users, there's always the wee-slack plugin [0] which runs on the Slack API, rather than the IRC gateway. [0] https://github.com/wee-slack/wee-slack
Does anyone know if there is an equivalent for irssi? Perhaps it's time I give weechat a try :/
I've yet to find one, which is unfortunate because I am a much bigger fan of irssi.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#89Okay, 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.
> Afterwards it's client developers' problem
Riiiight. And how many clients do you know that have that? Or read receipts? Or file sending? Or... Or...?
There’s basically just one client that supports modern XMPP features. So no, it’s not the client developers’ problem. It becomes the end-users’ problem. And they will abandon XMPP in favor of solutions that don’t have tgat problem.
Re: Tell HN: Slack decides to close down IRC and XMPP gateways
#90For weechat users, there's always the wee-slack plugin [0] which runs on the Slack API, rather than the IRC gateway. [0] https://github.com/wee-slack/wee-slack
Does anyone know if there is an equivalent for irssi? Perhaps it's time I give weechat a try :/
wee-slack is the reason I switched from irssi to weechat.
Sad, but true.