Ticket UUID: | e3cb73609711072c78d57b6e5d2cd2ec7bb46410 | |||
Title: | Some Slack user names not being populated | |||
Status: | Closed | Type: | Bug | |
Severity: | Minor | Priority: | Low | |
Subsystem: | Slack | Resolution: | Fixed | |
Last Modified: | 2019-07-04 17:51:05 | |||
Version Found In: | 0.4.3 | |||
lexy — 2019-05-02 11:16:03 When joining a developed Slack community, Ripcord can't retrieve all user names and shows I suspect that this is because of Slack Rate Limits. I wish Ripcord honored these limitations and somehow queued or delayed failed requests instead of making it more cumbersome for the user. Thanks! | ||||
cancel — 2019-05-02 22:55:39 Ripcord already honors the Slack rate limits. User name querying is not rate limited, anyway, and occurs over WebSocket and not HTTP requests. Could you provide me with more information? | ||||
lexy — 2019-05-04 18:14:58 If I get a message from this user, Ripcord will show me user's Like this in the chat list:
or this in the chat:
Images don't seem to load well, check these links: https://a.radikal.ru/a43/1905/1d/ecdad68eea9b.png https://c.radikal.ru/c10/1905/3f/e5317c51f792.png | ||||
lexy — 2019-05-17 14:29:55 I think I know why this happens. If some users are members of this enterprise grid, but not members of this workspace, they will display as ...... in Ripcord. Direct conversations are displayed throughout the whole grid, even if some people are not members of the workspace I am connected to. | ||||
cancel — 2019-06-19 11:49:44 Ok. It seems I don't have access to a Slack instance where I can reproduce this, so I'm not sure what to do. | ||||
cancel — 2019-06-29 17:30:30 Fixed in next release |