4 ms·

I'm not an expert on Zulip by any means but I'm always a fan of other open source projects. Beyond what we have right now, we want to design Linen to be a thre

I'm not an expert on Zulip by any means but I'm always a fan of other open source projects. Beyond what we have right now, we want to design Linen to be a thread-first tool (hence the name). We wanted an experience familiar to users of chat communities but encourages thread usage natively. We want to do things like letting you move messages between threads and threads between channel. Which I think Zulip has that functionality. We just haven't had the chance yet because the scope is so big and we wanted to ship something quick and get early feedback. Would also love to hear about what you really enjoy about Zulip.

ghostpepper 4y ago
Threading is the killer feature of Zulip I think
- dizhn 4y ago
  Yes and conversation histories can be published too.
v3ss0n 4y ago
Zulip have publicweb channels support which is totally google indexable. Check rust community
cheeseblubber 4y ago
I've also mentioned this in a separate comment in the post but reposting here for visibility: To clarify Zulip let's you export their conversations and then render it by generating a static HTMl similar to https://leanprover-community.github.io/archive/ https://leanprover-community.github.io/archive/ You'd have to use https://github.com/zulip/zulip-archive https://github.com/zulip/zulip-archive to achieve. You can see it in the Caveats sections in their documentation https://zulip.com/help/public-access-option#caveats https://zulip.com/help/public-access-option#caveats They are working on it here: https://github.com/zulip/zulip/issues/21881 https://github.com/zulip/zulip/issues/21881 Zulip lets you browse conversations of public conversations but that is very different than the app being natively search engine friendly and indexable. The difference between Zulip's implementation and Linen is that you don't need a separate UI when someone finds a link in Google. If you find a link through Google you get a dynamic real time experience instead of a static page. If you google site:rust-lang.zulipchat.com you won't see any results. If you do the same with site:slack-chats.kotlinlang.org you'll see at least 20,000 results

ghostpepper 4y ago

Threading is the killer feature of Zulip I think

dizhn 4y ago
Yes and conversation histories can be published too.

v3ss0n 4y ago

Zulip have publicweb channels support which is totally google indexable. Check rust community

cheeseblubber 4y ago

I've also mentioned this in a separate comment in the post but reposting here for visibility: To clarify Zulip let's you export their conversations and then render it by generating a static HTMl similar to https://leanprover-community.github.io/archive/ https://leanprover-community.github.io/archive/ You'd have to use https://github.com/zulip/zulip-archive https://github.com/zulip/zulip-archive to achieve. You can see it in the Caveats sections in their documentation https://zulip.com/help/public-access-option#caveats https://zulip.com/help/public-access-option#caveats They are working on it here: https://github.com/zulip/zulip/issues/21881 https://github.com/zulip/zulip/issues/21881 Zulip lets you browse conversations of public conversations but that is very different than the app being natively search engine friendly and indexable. The difference between Zulip's implementation and Linen is that you don't need a separate UI when someone finds a link in Google. If you find a link through Google you get a dynamic real time experience instead of a static page. If you google site:rust-lang.zulipchat.com you won't see any results. If you do the same with site:slack-chats.kotlinlang.org you'll see at least 20,000 results