![]() However, when you're "in" one Slack workspace, all the rest can sort of disappear by the wayside. We want something that keeps our Slack more present. ![]() Our devs could, of course, open Tighten's slack in their browser. But even with pinned tabs, browser windows still sort of ebb and flow an individual item in a browser doesn't get its own cmd-tab and the browser doesn't get quite the same quality of some of the keyboard shortcuts and other system integrations.Īll-in-all, Slack in a browser window is fine, but a second-class citizen. ![]() I didn't mention this in the original version of this post because I consider it helpful but separate, but enough people mentioned it that I figured I would add it. Recently Slack added a brilliant feature called shared channels that allows you to sync a channel between your Slack and another workspace. If you can handle your communications with the other workspace within one or a few channels, and you have a relationship set up such that shared channels will work, that's absolutely the best way to go about it. You can avoid the slow-down of multiple workspaces but still get the benefits of collaboration. This tip is from Tightenite Dave Hicking: The remaining options-and the less-desirable options above-assume you're in a context where that's not an option. You can duplicate the Slack application file (using Finder) on your Mac and rename the second version, and then you'll just have two instances that you can open side-by-side. Pro: You get the full power of desktop Slack on both.Ĭon: If you have more than one workspace, you're now spinning up two instances of a local Slack instance with multiple workspaces. Slack uses up a lot of memory, and two full local Slack instances connected to multiple workspaces each will really amplify that. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |