-
Notifications
You must be signed in to change notification settings - Fork 176
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Self-hosting the twemoji script until I can get a replacement
- Loading branch information
1 parent
24d71bd
commit f56858b
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f56858b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could just package the script with LiveBot, but this way I can update the twemoji script from my web backend, and don't need to update LiveBot every time a new twemoji API update happens.
Why is this change happening at all? Maxcdn is now called Stackpath, and they are not hosting the twemoji CDN anymore. So, because at the time of writing, no new API has officially taken it's place and is not relying on maxcdn anyway. So, I'm hosting the min.js file, modified to point to
https://jsdelivr.net/gh/tweitter/twemoji@14.0.2/assets/
for the images. This works, so it'll stay for a while :)