Skip to content

Instantly share code, notes, and snippets.

View dotWee's full-sized avatar
🧑‍🎨
N06 G41 G00 X1.1 Z1.1 T0303 M08

Lukas Wolfsteiner dotWee

🧑‍🎨
N06 G41 G00 X1.1 Z1.1 T0303 M08
View GitHub Profile
@dotWee
dotWee / giphy_webp_to_gif_redirect.user.js
Last active October 31, 2024 18:10
UserScript to redirect .webp links to the equivalent .gif file url
// ==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
@dotWee
dotWee / .cursorrule
Created March 10, 2025 12:09
Cursor rule for git commits
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