zulip-archive VS matterbridge

You can do search engine indexing via https://github.com/zulip/zulip-archive; it defaults to archiving your public access streams.

We will eventually support search engine indexing without the extra overhead of running a separate archive tool (likely as an organization-level settings checkbox, since not everyone who wants public access wants search engine indexing).

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/ 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 has both a business model and an official archiving tool.

Yes, the web-public view is being actively worked on: https://github.com/zulip/zulip/issues?q=label%3A%22area%3A+w...

There’s also a separate zulip-archive project that exports Zulip streams to static HTML: https://github.com/zulip/zulip-archive

Search engine indexing is available in Zulip today via Zulip's public archive tool (https://github.com/zulip/zulip-archive). Many larger OSS projects using Zulip, like Rust, Julia, and Lean Prover, use it.

We expect to have a native feature allowing a configurable set of streams to be browsed using a real Zulip web app UI without creating an account, available in beta in the next few weeks; we're actively integrating the implementation via https://github.com/zulip/zulip/pull/18532.

We plan to look at optional search indexing in that native implementation once the logged-out access feature is complete complete.

I lead the Zulip project.

I'm not sure about this detail of Slack's ToS. At a technical level, you can certainly export your data from a Slack (which is we implement https://zulip.com/help/import-from-slack); I imagine it's easy to write a tool to format and publish it.

FWIW Zulip maintains https://github.com/zulip/zulip-archive, which is a configurable API-based tool for creating a static HTML archive from a Zulip organization, with tooling to update it every few minutes. A lot of larger open projects use it. (We're also working on a native logged-out access feature with less janky formatting, which has a working PR that we need to integrate).

I suppose you could export your data from Slack, import it into Zulip, and then publish that using zulip-archive if you didn't want to write any code, but I'm sure the formatting would be better preserved if one avoided the "convert Slack markup to Zulip markup" step.

It's quite sad Slack and Discord are often the first choice for open communities. They are siloed and unless you are deliberately searching in a specific workspace, you'll never run into the information in a search engine.

In comparison, Zulip:

- provides HTML export functionality https://github.com/zulip/zulip-archive#zulip-html-archive (example https://leanprover-community.github.io/archive )

- URLs are nice and encode meaning (e.g. https://memex.zulipchat.com/#narrow/stream/279601-hpi/topic/...)

All of them. :)

https://github.com/42wim/matterbridge

An involved alternative is to access whatsapp through a matrix bridge. It requires either paying for hosting or figuring out how to host a matrix server and the whatsapp bridge [1]; I do the latter and can attest it's not very hard if you have a technical background (and you're on hn, so you probably do), but YMMV. There's a lot of matrix clients, all of which open source; and the whatsapp bridge works really well nowadays, enough that I've been using it almost exclusively for my texting (no whatsapp calls tho).

In fact, I recently bought a non-smartphone running KaiOS, and use whatsapp through a matrix client, chooj - which, although in early alpha, works well for my use case of accessing whatsapp while outside the home without having to carry an addictive smartphone with me. KaiOS does have a native whatsapp app, but it does not support whatsapp web at all, and that is an absolute necessity for me, especially when typing requires (bad) T9.

My point is, matrix bridges afford A LOT of freedom with how to access whatsapp (and other closed-source communication apps), if you're willing to deal with some friction. And now they're stable and mature enough that they work pretty darn well - no doubt thanks in part to support from beeper [2], which funds development for several major bridges. Within the android ecosystem, beeper is probably the easiest way to gateway all your communications through matrix, though I have no experience with it. Sounds like paid matrix+bridge hosting, plus a generally much nicer and frictionless experience.

[1]: https://github.com/42wim/matterbridge

[2]: https://www.beeper.com/

We use matterbridge to bridge IRC to matrix at https://tetaneutral.net

https://github.com/42wim/matterbridge

It's a chat bridge for different platforms. https://github.com/42wim/matterbridge

I personally use matterbridge to bridge between specific IRC channels and specific discord server channels, and run it on a FreeBSD server. Packages are available for it on the BSDs and major Linux distributions. Follow the instructions for configuration and enable its service as appropriate on the OS.

https://github.com/42wim/matterbridge perhaps?

Hi, I'm looking for an easy to use automation tool for my company. There are tons of projects out there and I find it hard to pick one among them. I found : - hugging - n8n - beehive - flogo - metterbridge - node-red

As for the use case op hopes for -- the matterbridge project might be relevant. Ideally, you could migrate the history to a Mattermost server and set up the bridge. The Mattermost server will log all future communications automatically. The benefit of this over a pure archive (HTML or PDF type) is that the archive itself is a full-featured workspace ready to be used standalone at any time, should any issues arise from Slack.

Oh, interesting! It seems like an alternative to MatterBridge but for 1 to 1 bridging.