You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case that fetching the list of emotes through a provider fails, there should be a cached response to fall back to. This doesn't sound like a nightmare to implement, and would be imo a huge QoL change. It would feel great to still see emotes when a service is having a hiccup, especially since emote images/gifs are already getting cached.
To avoid any confusion, there should still be a system message when a cached response is used indicating that the request has failed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the case that fetching the list of emotes through a provider fails, there should be a cached response to fall back to. This doesn't sound like a nightmare to implement, and would be imo a huge QoL change. It would feel great to still see emotes when a service is having a hiccup, especially since emote images/gifs are already getting cached.
To avoid any confusion, there should still be a system message when a cached response is used indicating that the request has failed.
Beta Was this translation helpful? Give feedback.
All reactions