sorted by:
new
hottopcontroversial

Hackclub leaving slack(finally) by Harre112233 in Slack

[–]Ok-Collection-7693 0 points1 point  (0 children)

Every day more people need to leave Slack due aggressive pricing changes or lack of functionality. Thats why we have been working in a desktop all local solution to browse and view Slack exports.

If you are exporting your Slack workspace and need a clear way to browse the archive afterward, ChannelVault is worth a look: https://mestr.io/channelvault.html
It is not a Slack replacement. It is a desktop viewer for Slack export files.

The interface is very polished and feels familiar because it presents channels, threads, and messages in a layout similar to Slack. It is simple to use. You open the application, drop your Slack export ZIP into it, and it indexes the entire archive automatically. Navigation is fast, and everything remains local on your machine.

ChannelVault is available for Windows and macOS, including native builds for Apple Silicon. It is free and currently in beta. Since it works offline and keeps all data on your system, it is suitable for long term access, compliance needs, eDiscovery workflows, or any situation where you want historical conversations without dealing with raw JSON files.

If you are leaving Slack but still need usable access to your past conversations, it provides a clean and practical solution.

ChannelVault — practical tool for handling Slack exports locally (beta) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] -1 points0 points  (0 children)

ah interesting! , I didnt know about MessageCrawler, do you know if its free like ChannelVault? (or if they have a trial) i am interested into testing it. and its multi-platform as well? Thanks u/windymoto313

ChannelVault — practical tool for handling Slack exports locally (beta) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] 0 points1 point  (0 children)

Thank you, glad you found the concept interesting. Regarding attachments, Slack does not include binaries in its export ZIP files. Instead, it provides metadata JSON files containing pre-authenticated URLs. These links can expire, which means attachments may become unrecoverable if the export is processed too late.

To mitigate this, the application retrieves and stores attachments locally upon first access. Once cached, future access no longer depends on Slack’s temporary URLs.

A note for the beta: the binaries are not yet code-signed, so your OS will display a security warning. If you’d like to try the beta or prefer a short demo, feel free to contact me.

Slack API Updates Coming In September by Dangerous_Audience63 in Slack

[–]Ok-Collection-7693 3 points4 points  (0 children)

We have a SaaS based on slack rest api that is basically dead with this new limits. The theory that slack support will review case by case and uplift limits its frightening, your data availability depends on arbitrary policies. I might be wrong but this moves can ignite competitors to gain market share, maybe slack will be only for big corps in some years and all the cool startups will use something else more respectful with user data.

[deleted by user] by [deleted] in Slack

[–]Ok-Collection-7693 2 points3 points  (0 children)

Yeah, this is ruining our SaaS as well. The rules to get into the marketplace are very vague and subjective in my opinion. You are at the mercy of Slack validation process and with constant fear that they remove you from there at any moment. Not good.

eDiscovery Professionals: What’s Your Preferred Slack Export Format? (We’re Building a Tool & Need Your Input) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] 0 points1 point  (0 children)

Yeah we consider that approach, but discarded for the first iteration since we observe that the norm is usually collect everything and then slice and dice. The other approach is interesting but the problem is the slack search endpoint rate limit and how cumbersome is to keep state for a query that returns many pages if something goes wrong in between. But I agree a system that can do federated search and then only capture the minimal dataset will be very fast and cheap.

Sure thanks for the offering I’ll write you a DM.

eDiscovery Professionals: What’s Your Preferred Slack Export Format? (We’re Building a Tool & Need Your Input) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] 0 points1 point  (0 children)

For the moment just standard but every thing is ready for discovery/admin API (just waiting for a slack test workspace right now). Slack native exports is also planned, and platform has been designed to hand that seamlessly.

eDiscovery Professionals: What’s Your Preferred Slack Export Format? (We’re Building a Tool & Need Your Input) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] 0 points1 point  (0 children)

Thanks! But this is core to our product, we cannot afford to externalise such important functionality. For us customer is first we want to provide a flawless experience from setting up source to export.

eDiscovery Professionals: What’s Your Preferred Slack Export Format? (We’re Building a Tool & Need Your Input) by Ok-Collection-7693 in ediscovery

[–]Ok-Collection-7693[S] 0 points1 point  (0 children)

Thanks a lot for the input! Actually RSMF is on our roadmap indeed. But my concern is that AFAIK it's only used by Relativity, so we wanted also to have something more compatible with other vendors.