5 ms·
Big fan of Zulip. Only problem is that you don't get email notifications unless you're directly @ mentioned in a response, even if you're participating in a dis
by bachmeier 4y ago
Big fan of Zulip. Only problem is that you don't get email notifications unless you're directly @ mentioned in a response, even if you're participating in a discussion, and even if they're replying directly to you. Otherwise I find the threading approach to be a big win.
- vitro 4y agoYou can set up Alert words in your personal settings and when that word appears in the chat, you will get notified as well.
- bachmeier 4y agoI haven't had much luck with that. Here's an example of where you run into problems: "You can do that by changing your code like this: [code] Let me know when you have the results." "Okay, but I'm going to be busy for the next few days. Will post here when it's done." {Three days later}: "Your suggestion worked! Let me know how to proceed from here." You can either keep Zulip open all the time - which makes me cringe - or you can go without any form of notification. Then a week later you decide to check back and see the message, but they forgot to @ you.
- philip1209 4y agoWhen I was building MoonlightWork.com, we had ~3x the DAUs on Email that we did on our website. So, I strongly believe that good email summaries are key to async comms. I'm working on a similar threaded messages project called Booklet (https://booklet.community https://booklet.community), and I think good email summaries are the key to the product. It's hard to do, but there are some cool data opportunities to improve relevancy.
- tabbott 4y agoThanks for the feedback! We're planning to extend our notifications system model to let you specify a configurable policy for which topics one wants notifications for. In particular, a lot of preparatory refactoring towards supporting this has been merged over the last year, and we have a contributor planning to focus on this project over the summer. https://github.com/zulip/zulip/issues/12309 https://github.com/zulip/zulip/issues/12309 is probably the right issue to follow for now. My plan for today included writing a much more technical version of that issue with a specific implementation plan, before someone submitted Zulip to Hacker News :).