Settings and activity
3 results found
-
24 votesCanla supported this idea ·
An error occurred while saving the comment -
17 votesCanla supported this idea ·
-
7 votes
We will be updating the documentation to make it clearer that the image in the payload will always be a static image. We are also planning to document the URL schema for the CDN to retrieve the animated version.
An error occurred while saving the comment Canla commentedTo clarify, I understand that the /v1/ and /v2/{emote_id}/static/ CDN urls are always static pngs for all emote ids, but the currently undocumented /v2/{emote_id}/default/ CDN urls you mention for the animated ones can either return pngs or gifs for emotesv2_ emotes depending on the emote without any way to tell beforehand from the API responses what type any emote with a emotesv2_whatever id will be without downloading it.
examples from dansgaming:
https://static-cdn.jtvnw.net/emoticons/v2/emotesv2_5dc74153d9bb4a13a7f6d8b37f318258/default/light/3.0
both emotesv2_ ids, one is a gif, one is a png. From the API alone you can't tell what type it will be.Canla shared this idea ·
At least having a checkbox on password change thats like "reset all 3rd party connections/tokens" and checked by default so anyone can opt out if they know and don't want it would be nice.