91–100 of 624 posts
Is Mattermost a viable alternative, and is it possible to bridge it with IRC and XMPP?
[1]: https://github.com/42wim/matterbridge [2]: https://matrix.org/
Earlier quoted context omitted.
> 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.
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…
One problem with all these closed client apps slack (with this update)/whatsapp/telegram is that there is no way to verify/audit it is actually doing proper e2e.
Users must trust the X company that they are really doing proper e2e.
These apps should allow users to download a plugin and use that to produce the e2e. Then the user would be able to download an open sourced audited plugin that encrypts the messages before they hit the whatsapp/slack/telegram company servers.
So for instance, if this was possible, everyone on a group would download and install the plugin that runs on top of whatsapp/slack/telegram and share an encryption key that only they know about. And do the same for conversations between 2 people.
There must be some point of trust, however with the current situation, it is hard to trust e2e code no one is able to audit.
Or just open the protocol so everyone can use and create their own clients and their own e2e mechanisms. Which is what IRC is.
Earlier quoted context omitted.
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: http://cultofthepartyparrot.com
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.
Weird, my slack app on windows is currently using 54MB.
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.
Bitlbee will compensate.
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…
Moxie Marlinspike has a blog post about why protocols like XMPP aren't good enough to support modern messaging apps. https://signal.org/blog/the-ecosystem-is-moving/ XMPP is an example of a federated protocol that advertises itself as a “living standard.” Despite its capacity for protocol “extensions,” however, it’s undeniable that XMPP still largely resembles a synchronous protocol with limited support for rich medi…
IRCCloud is using only standard IRC features to implement their Slack gateway that offers all features of slack - including reactions and threads.
Federated protocols can move extremely quickly, I've seen that myself recently.
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'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.
(I'm not saying the current open protocols are perfect, or even close, however - 100s of closed chat protocols have been built and rebuilt - that effort would have been better spent in the open IMO. Obviously, investors and similar business functions see things differently though.)