Blog post: Introducing SDriver: a Delphi wrapper for Slack API
Blog post: Introducing SDriver: a Delphi wrapper for Slack API
https://blog.andreamagni.eu/2017/01/introducing-sdriver-a-delphi-wrapper-for-slack-api/
https://blog.andreamagni.eu/2017/01/introducing-sdriver-a-delphi-wrapper-for-slack-api/
https://blog.andreamagni.eu/2017/01/introducing-sdriver-a-delphi-wrapper-for-slack-api/
https://blog.andreamagni.eu/2017/01/introducing-sdriver-a-delphi-wrapper-for-slack-api/
Seriously, I'm going to have a look at this Slack thing. It looks really really good
ReplyDeleteAgustin Ortu I extensively communicate with my client with wechat mobile - what are mostly useful are the voice messages, pictures and short-videos - for example, the client can instantly take a picture of my product with his phone's camera. And the voice messages are really time savers, as opposed to text msg. So the last time I thought, it'll be great if wechat supports channels like slack, for separating different topics. So I had a look at Slack, but unfortunately, it doesn't support voice msg, and that's a showstopper for me. Re. this wrapper by Andrea, it's great of course!
ReplyDeleteI'd expect voice messages to be possible using a slack app
ReplyDeleteAgustin Ortu I think Slack is less useful than advertised. The lack of some kind of threading (separation of messages by subject) makes long discussions virtually impossible. It also does not make sense if you need to go back to that subject in the future (you would have to search for exact terms in order to find it). So... all in all... looks to me like a social media for companies. You post some short message there and all channel subscribers will be informed about that (if the channel is not used much. Otherwise your message will probably be lost in the middle of dozens of others)
ReplyDeleteAlexandre Machado Channels are how you segregate discussions by subject
ReplyDeleteDavid Heffernan And groups is how you can do that by people involved (developers, sales, PR, ...)
ReplyDeleteNo David Heffernan it is not. Do you use Slack?
ReplyDeleteAlexandre Machado It's the only mechanism to give a conversation a subject. So yes, channels is how you do that. Perhaps you have scope to improve your usage before you write it off.
ReplyDeleteAndrea Magni that doesn't get me anywhere if I want to discuss different topics with the same group of people. So I think that's a higher level of segregation, but still useful.
ReplyDeleteDavid Heffernan I use slack in a daily basis for more than one year and, again, it is not. In a correspondence with EMBT forum, a slack channel is just like an EMBT forum category. So, you would have in Slack: Non Tech, General and Database channels. Channels are static. You don't create and archive channels everyday in Slack. If someone is discussing a DBExpress bug in your Database channel and some other guy decides to post another message about a new feature in FireDAC in the same Database channel both discussions get mixed and someone trying to follow just one of those discussions isn't able to do so, without reading all messages and deciding which one belongs to each discussion. You cannot separate the discussions like you do in a forum, and you cannot get back to a discussion a few days later to include some more information.
ReplyDeleteAlexandre Machado slack channels can be created as often as you like. If you want a discussion on a specific topic, create a private channel and add whoever needs to be part of the conversation. When it's done, archive it. This is how it is meant to be done. Channels don't need to be static. Many are but they don't all have to be.
ReplyDeleteYou say that discussions can't be segregated by topic but my experience is different. My team has no trouble doing exactly that.
You might have been using slack for a year but it seems that you have scope to improve your usage considerably.
David Heffernan you are talking about private channels and group messages. Interesting that Slack seems to share this exact concept of channel: https://get.slack.help/hc/en-us/articles/201925108-About-channels-and-direct-messages
ReplyDeleteSpend a few minutes watching the "Communicating with Channels" video and maybe you get it. The fact that you are creating and archiving channels all the time, just shows how deficient the tool is. It was not meant to be like that.
Or do you see "Engineering", "Accounts" and "Marketing" channels being created and archived several times a day within a company?
Alexandre Machado No, those channels would be static. How does that relate to what I am talking about. Anyway, it's obviously up to each of us how we use our tools. If you prefer never to create private channels that's up to you.
ReplyDeleteSure, David Heffernan, finally!!! As you can see, I was describing to another user my impressions about Slack. You decided to step in with your absolute truth about that subject, remember?
ReplyDeleteAlexandre Machado Stating that separation of messages by subject was not possible seemed like you were asserting absolute truth. If that was just you expressing a personal opinion I am sorry that I mis-interpreted that opinion as something stronger. Anyway, I think it's clear now that messages can be separated by subject.
ReplyDeleteAlexandre Machado What about this :-) ? https://slackhq.com/threaded-messaging-comes-to-slack-417ffba054bd#.n4s6yiaqi
ReplyDeleteAndrea Magni I already knew this. This has been an old demand. But please tell them to stop the threading development, because seems that the slack dev team just don't know how to use it. ;-)
ReplyDelete