slackapi / node-slack-sdk

Slack Developer Kit for Node.js
https://tools.slack.dev/node-slack-sdk/
MIT License
3.27k stars 662 forks source link

Typing indicator in Events API? #1130

Closed arkdev9 closed 3 years ago

arkdev9 commented 3 years ago

Description

Is there any functional equivalent of the sendTyping function in RTM for Events API?

What type of issue is this? (place an x in one of the [ ])

Requirements (place an x in each of the [ ])


Packages:

Select all that apply:

stevengill commented 3 years ago

hey @rogueDev9,

There is no equivalent functionality in events-api and we don't plan on introducing it.

We know from our user research that people prefer interactive apps most of the time over conversational bots. so we've been building features like App Home, Block Kit, and Modals to make bring those interactions to life. Ultimately, if you want to pretend your bot is typing, you can do it by sending a "@my_fun_bot is typing" message from the app, and then removing it after you send your actual message. Better yet, you can send a spinner or other animation in an image.

arkdev9 commented 3 years ago

Got it thanks for the clarification

gusman80 commented 10 months ago

with all the chatgpts around , their streaming api and their latency on longer threads i think you should overthink this ...

boutcher commented 7 months ago

Totally agree with @gusman80 ... Have Slack front-ending an OpenAI Assistant, sometimes there's 20-30 seconds to get a response. Not seeing any indication of work being done ("bot is typing") makes for a really awkward experience.

zimeg commented 7 months ago

@boutcher still no update on introducing a typing indicator, but you could consider using the 🤔 emoji with reactions.add then reactions.remove to signal your app is thinking? I might've seen @seratch use this before!

seratch commented 7 months ago

Yet another approach for this is to repeatedly call chat.update with chunk of gen AI response text. My example app utilizes the technique.

dkarlovi commented 4 months ago

@seratch how are the rate limits here, do you do batching or do you just stream the LLM responses as they come in?

seratch commented 4 months ago

@dkarlovi chat.update's rate limit is Tier 3, which means you can call it 50+ times per minute (per app and per workspace). In most cases, you won't receive an error, but if you're building an app for a busy workspace/org with a large user base, adjusting the frequency of repeated updates may be worth considering.