Skip to content

Comment on Slack updates retention policy for free workspacesparent

Comments

Yeah, totally. If it's private then it's up to whoever owns it. I think my experience is colored by using Slack for a group that's very much intended to be a public record: https://futureofcoding.org/community

Perhaps a better way to state my position is: I think publishing should be a ratchet. Everyone can choose what they want to make public. But once it's public that's it, there's no undo and no do-over. This isn't ideal in some situations, but on balance seems like the greater good. Stuff gets added to the commons of human knowledge, and we do our darnedest not to let stuff get removed once it's been added.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.