Nope! You won't be able to click on links for the foreseeable future. I'm hoping it's still useful just to bounce around between crosslinks. And search.
There can also be a port atop Linux. With networking but no avatars. That's probably a good trade-off 😄
Here's a release you can try out of my network-less offline-only read-only browser for FoC archives:
http://akkartik.name/mu/mu-slack-browser-20210811.img.gz (70KB)
http://akkartik.name/mu/foc-data-20210811.img.gz (16MB)
Download and gunzip
both, and then run (using Qemu on Linux):
qemu-system-i386 -accel kvm -m 2G -hda mu-slack-browser-20210811.img -hdb foc-data-20210811.img
For other platforms, drop the -accel kvm
. But it'll be significantly slower (5-25x, depending on what acceleration you have available)
Even on Linux, the app currently loads all 55MB in the data disk (including uncompressed avatars) on startup, which takes around 3 minutes. (Edit: interestingly, I actually have the disk load up in just 30 seconds if I drop the -accel kvm
🤔)
After that 3-minute wait, all you get at the moment is a river-of-news view that mingles all posts and comments in strict reverse chronological order. Page up, page down, that's it. I plan to implement other ways to slice and dice items by channel, post, user.
Other known issues:
- This isn't a pure-Mu solution. I'm converting Slack archives to Mu data disk images using a Python script and a few other dependencies: https://github.com/akkartik/mu/blob/main/browse-slack/convert_slack.py
- No search yet, though I've got misleading placeholders in the UI.
- No message text parsing yet, so no hyphenation, no Unicode escapes, no translation of Slack
:emoji:
- ... (please report others!)
Things that are very far away: opening attachments and URLs, editing, reacji, anything that requires network access.
Does anyone have objections to publicizing these disk images more broadly? There's no DMs in them, and I know we consider the channels here to be a public record. But now it might be a lot more amenable to drive-by browsing. cc Ivan Reese Mariano Guerra
(Apologies for monopolizing this channel two days in a row. I didn't think things through with my over-excited teaser yesterday.)
📷 slack-browser.png
Whoa, it's amazing how much stuff I've been missing out on within comments.
The 3 main channels are archived on github so I don't see a problem with this one (or if there is then I have a problem too :D)
Yeah, I think it's fine to share the public slack discussions openly / widely.
Here's a release you can try out of my network-less offline-only read-only browser for FoC archives:
http://akkartik.name/mu/mu-slack-browser-20210811.img.gz (70KB)
http://akkartik.name/mu/foc-data-20210811.img.gz (16MB)
Download and gunzip
both, and then run (using Qemu on Linux):
qemu-system-i386 -accel kvm -m 2G -hda mu-slack-browser-20210811.img -hdb foc-data-20210811.img
For other platforms, drop the -accel kvm
. But it'll be significantly slower (5-25x, depending on what acceleration you have available)
Even on Linux, the app currently loads all 55MB in the data disk (including uncompressed avatars) on startup, which takes around 3 minutes. (Edit: interestingly, I actually have the disk load up in just 30 seconds if I drop the -accel kvm
🤔)
After that 3-minute wait, all you get at the moment is a river-of-news view that mingles all posts and comments in strict reverse chronological order. Page up, page down, that's it. I plan to implement other ways to slice and dice items by channel, post, user.
Other known issues:
- This isn't a pure-Mu solution. I'm converting Slack archives to Mu data disk images using a Python script and a few other dependencies: https://github.com/akkartik/mu/blob/main/browse-slack/convert_slack.py
- No search yet, though I've got misleading placeholders in the UI.
- No message text parsing yet, so no hyphenation, no Unicode escapes, no translation of Slack
:emoji:
- ... (please report others!)
Things that are very far away: opening attachments and URLs, editing, reacji, anything that requires network access.
Does anyone have objections to publicizing these disk images more broadly? There's no DMs in them, and I know we consider the channels here to be a public record. But now it might be a lot more amenable to drive-by browsing. cc Ivan Reese Mariano Guerra
(Apologies for monopolizing this channel two days in a row. I didn't think things through with my over-excited teaser yesterday.)
📷 slack-browser.png