71–80 of 96 posts
Slack is not a good enough replacement for IRC. Centrally controlled, heavy and bloated - nope, nope, it's just not it.
In my dreams I manage a locally-hosted Matrix homeserver in our company's VPN. (We're not big.) They just added voice calls via web UI. Not E2EE yet but if you're on an encrypted VPN then that's kinda moot anyway.
Earlier quoted context omitted.
In my dreams I manage a locally-hosted Matrix homeserver in our company's VPN. (We're not big.) They just added voice calls via web UI. Not E2EE yet but if you're on an encrypted VPN then that's kinda moot anyway.
I like the idea of Matrix, but - can you get simple, thin, GUI clients for it like you have for IRC? IIRC, most GUI clients for it feel like something running inside my web browser...
Seems to be more on the "glossy" and "web client" end of the spectrum in general but probably there is some reasonable compromise to be reached from the proliferation of different clients.
Earlier quoted context omitted.
Slack should at least bridge to an open protocol, if not use one outright, so I can use any client I want. Like they used to.
Ripcord [0] supports slack, but probably lacks a few features. It's very fast. [0] https://cancel.fm/ripcord/
This is more a service degradation / outage than an incident.
Earlier quoted context omitted.
In my dreams I manage a locally-hosted Matrix homeserver in our company's VPN. (We're not big.) They just added voice calls via web UI. Not E2EE yet but if you're on an encrypted VPN then that's kinda moot anyway.
I like the idea of Matrix, but - can you get simple, thin, GUI clients for it like you have for IRC? IIRC, most GUI clients for it feel like something running inside my web browser...
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...
This is not true in any way. Slack also have workspaces, channels, notifications, video calls, file sharing, admin tools and probably even more features. It's not just IRC.
Maybe writing a web-based app is lazy... except when you have to write native apps for macOS, Windows, Linux, Android, and iOS, and some people still need access via a browser. And each one has different ways of displaying images and videos and doing calls and handling file access. Now you have 5+ apps that you're maintaining, each with their own dedicated team since each one is unique. Want to roll out a new feature? Cool, now you have to write it 5 times across 5 teams. Good look coordinating that.
I know there are technologies that let you share code across all of the different native clients. But a webview wrapped in i.e. Electron handles most of it for you! Why would you do it any other way except to appease people who complain about bloat?
Earlier quoted context omitted.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...
Don't underestimate just how much devs can dig their heels in because they want to work in JS.