Struct is different. It's a reimagination of what a chat platform would look like if you were to completely give up the idea of chats in a serial log of channels (IRC, Slack, Discord), and embrace threads and feeds whole-heartedly. When everything is a thread, the platform can work remarkably well for users.
I don't understand why I'd need or want this. I saw it in the video and was horrified. Multiple feeds updating as I'm watching them is just too much going on.
When I'm chatting, I don't want to pay attention to 10 different things at once. I'm most productive when I am working on one task (with a single topic), which may require me to refer back to Slack periodically.
Struct looks like it has two differentiating features: 1) it surfaces irrelevant distractions in the All Threads channel, and 2) it creates the tl;dr summary. The former seems actively harmful to productivity, and the latter seems like it could be useful.
That's the beauty right -- you can control and filter what you see. As opposed to channel based interactions, where your boundaries are set in stone on channel creation.
I believe it does. You get a feed of all messages; and still organized by a topic, quite conveniently.
I don’t use it, though, since from anywhere in GUI I can immediately jump to the next unread message, irregardless of topic or stream, simply by pressing “n” on keyboard (preceded by Esc if I happened to be typing; my draft is saved reliably).
- https://zulip.com/help/inbox
For large and small companies surely the best way to maintain their users
Demanding SSO from Zulip would be like demanding SSO from self-hostable Discourse, Jitsi, etc.
First-class topics, tools for organizing messages between streams & topics, open-source self-hostable, no engagement of ML out of the box (but probably possible thanks to Python plugin support), Vim-like keyboard shortcuts.