3 ms·
It might be more useful to speak in general terms than call out Slack in particular. The concerns expressed here aren't limited to Slack (despite the link-bait
by otterley 10y ago
It might be more useful to speak in general terms than call out Slack in particular. The concerns expressed here aren't limited to Slack (despite the link-baity title), but any form of communication that:
(a) Can't be referenced or linked from the Web, and
(b) Is a form of synchronous communication
The same factors, BTW, apply equally to in-person discussions held at open source conferences. I wonder what the author thinks of the value of those insofar as "open source communications" are concerned.
- pseudalopex 10y agoAre there any open source projects that coordinate development or provide support primarily through in-person discussions at conferences?
- steveklabnik 10y agoI don't know about "primarily", but it's certainly an important aspect overall for many projects.
- michaelmior 10y agoExcept with both Slack and Gitter (not sure about others) you can link to specific messages. Sure you still need membership to view the content (a serious downside), but saying you can't link at all is disingenuous.
- otterley 10y agoWith Slack, at least, channel history is truncated for free accounts; so it's quite possible that a specific conversation could become practically inaccessible after a while.
- RyJones 10y agoYou are able to export your entire public history, regardless of the status of your account. I was able to do this to rescue the chat history for Hyperledger[0][1] before we moved to Rocket.Chat. [0] https://github.com/hyperledger/slack-archive https://github.com/hyperledger/slack-archive [1] http://slack-archive.hyperledger.org/html/index.html http://slack-archive.hyperledger.org/html/index.html