This file contains hidden or 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
// ==UserScript== | |
// @name Giphy webp to gif redirect | |
// @description Giphy: Redirect .webp links to the equivalent .gif file url | |
// @match *://*.giphy.com/media/*/giphy.webp | |
// @run-at document-start | |
// @inject-into content | |
// @version 1.1 | |
// @author Lukas Wolfsteiner <https://lukas.wolfsteiner.media> | |
// @updateURL https://gist.github.com/dotWee/56ba0251f12f83710f7db40367fcfebe/raw/giphy_webp_to_gif_redirect.user.js | |
// @downloadURL https://gist.github.com/dotWee/56ba0251f12f83710f7db40367fcfebe/raw/giphy_webp_to_gif_redirect.user.js |
This file contains hidden or 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
Commit Messages must have a short description that is less than 50 characters followed by a newline and a more detailed description. | |
- Commit message should have one of the following prefixes: "feat: ", "fix: ", "refactor: " | |
- Use markdown syntax | |
- Write concisely using an informal tone | |
- List significant changes | |
- Do not use specific names or files from the code | |
- Do not use phrases like "this commit", "this change", etc. | |
- Sentences in the detailed description should be separated by newlines | |
- Mention implications and possible usages of the code changes | |
- Do not respond as code with ``` on the start and end |
OlderNewer