Slack’s brand-new feature has an unexpectedly rich backstory

Post by prng2021 » Fri, Sep 23, 2022, 12:23 AM UTC

dogecoinbase wrote: post #31

davidmurdoch wrote: post #7

I wonder how this will work with slack orgs with short data retention policies. It wouldn't make sense to delete parts of a Canvas, as "Canvas docs are collaborative, and all their comments are just Slack threads." (from https://www.theverge.com/2022/9/20/23361717/slack-canvas-doc... )

Bear in mind that at this time, and for many years, data retention policies simply do not apply to uploaded files in a given channel (IIRC it does apply to global retention, but I'm not totally sure of the current behavior). There's a sensitive channel with a short retention period in a Slack for a company I do some consulting for and every few months I remind the admins that images/PDFs/etc that are uploaded to the…

Post by jononomo » Fri, Sep 23, 2022, 12:39 AM UTC

Post by inhumantsar » Fri, Sep 23, 2022, 4:04 AM UTC

fooby wrote: post #20

muglug wrote: post #14

Earlier quoted context omitted.

It is great! I work at Slack, where we've been testing that functionality for a while, and I use it for one-on-ones with remote colleagues. Huddles become like Zoom calls, but with much more context.

Is there any love for discord style "drop-in" voice channels? I'm never going to start a huddle in a channel of 30 people and say "its optional" -- but with a voice channel, people can see we are idling / chatting nonsense and join as needed.

Post by BerislavLopac » Fri, Sep 23, 2022, 6:11 AM UTC

db48x wrote: post #36

jacobr1 wrote: post #33

Earlier quoted context omitted.

But also "what is documentation?" You can have great customer-facing-product-docs and keep them up to date. You can have an internal process wiki that is mostely up to date. But what about the conversation over lunch/slack to change a product feature, that then becomes a story card, that gets mockup, that gets notes in the pr and comments in the code, that get ad-hoc slack conversations clarifying details. How many m…

Long ago Mozilla started making all such decisions on mailing lists, because the meetings at water coolers never get documented, and because you can't meet a colleague who lives 10,000 miles away over a water cooler (or at least not very often).

Post by puyoxyz » Fri, Sep 23, 2022, 12:07 PM UTC

paxys wrote: post #28

ttr2021 wrote: post #5

Yet another 'digital container' of disparate information to house your data and make it difficult for someone find it across an organisation. As someone who was working in a scale up I found that we had information spread across coda, wiki, markdown, tickets, collaborative whiteboards (Miro), git issues, google docs, coda, (insert random lastest cool SaaS that someone stumbled across one night and used the company ca…

> It just seems like it's not the tool itself, it's more there are actually too many options out there And that's exactly why every company is building their own version of such a tool. They all want to be the "one place" where all information is stored.