Our great sponsors
-
-
zulip-archive
Generate a static HTML archive of messages in any combination of streams in a Zulip organization.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Zulip
Zulip server and web application. Open-source team chat that helps teams stay productive and focused.
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Are you sure it's not self-hostable? https://github.com/Linen-dev/linen.dev/blob/main/docs/nextjs... seems to imply there's a local dev story. While I'm not familiar with next.js in order to know how dependent is is upon them, versus it's just "a handy place to run node apps," in my mental model if there's a local story there's a local docker-compose story
The AGPL part is a separate ball of wax entirely
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/ You'd have to use 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 They are working on it here: 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.
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/ You'd have to use 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 They are working on it here: 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.
> Mattermost and most open source chat tools not Google searchable.
This seems like a good idea for a bot built with https://github.com/turt2live/matrix-bot-sdk (which is very easy, I've used it for a few small projects).
The SDK has a callback for each new message - you could just put it into a DB and then render to static text.
Just a note to say that if you are using Matrix and want your conversations to be indexed in search engine ("Google-searchable"), you can deploy matrix-static[1] or you can use the live instance hosted by the Matrix foundation[2].
I think an interesting comparison, for both Linen and Matrix, would be to compare these 2 approaches: Linen natively indexed conversation and this Matrix "static" client. I would be especially interested by what additional features Linen provides in term of indexing compared to this static client.
[1]: https://github.com/matrix-org/matrix-static
(heads up that we're about to replace matrix-static, which powers view.matrix.org, with https://github.com/matrix-org/matrix-public-archive - which is a way better public archive interface for Matrix, built on Hydrogen)