The rest of the complexity is app-specific (e.g. The tricky part here is that you will need to track identify attributes of all messages sent to the user in order to thread updates under them. ![]() Regular messages for important messages (e.g.activities where I know that I already have users attention in a specific channel. Ephemeral messages for introductions to the #snack-club channel, i.e.Otherwise, the unpredictability of response_url availability means that sometimes messages are not delivered. After the first interaction, I switch to one of the following methods. Only using response_url for the response to the first interaction.Therefore the 5 request limit didn't work. I had a requirement to "count down" as the video is about to end (the videos are capped to 15 minutes). It is also limited how many times you can use (5). For every interaction, you have a response_url (a temporary webhook URL that you can use to generate messages responses). Slack API makes communication with the bot user a bit tricky. It is strange that there are no events for user presence change, though. every minute I pick 50 random users and I check their presence using the rate-limited getPresence API. I ended up asking Slack permissions to read list of workspace users and doing randomized checks every minute, i.e. I needed this functionality in order to identify who is available to snack. Turns out that Slack API does not provide any scalable way to check if users are present. What would seem like a straightforward issue, turned out to be one of the biggest headaches. How to find which Slack users are present? Note: I have later replaced Zoom integration with Twilio WebRTC as I needed more flexibility about the video experience. The tricky part was to discover the availability of the webhook events: the data about participants is not available via API. Knowing about Bolt would have likely saved a lot of time. I didn't know about it and didn't use it. Somehow it completely flew under my radar, but there is a Slack framework for building bots. If you are thinking of building something like this, here are some tips: Have a video conversation with someone else in your Slack workspace.I estimated it to be something I can turnaround over the weekend, but instead it ended up over 70k lines of code. What I didn't expect is just how complex this is going to be. (Video shows slightly outdated user-experience. I ended up building: Snack, a sort of chatroulette for Slack (but without d*cks □). It is just lacking that element of "water cooler" conversations. I decided to make a Slack bot since this is the tool that every team will be using already. I can ease their transition by creating a virtual medium for having serendipitous conversations with their team. They are used to staying in sync with their team through unplanned conversations that happen every day in the office (but don't happen online). Ī lot of people are transitioning to WFH. A couple of weeks ago, I have entered a COVID themed hackathon organized by.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |