| Here's how to install a userscript from a GitHub Gist in Firefox for Android. | |
| ### 1. Install a Userscript Manager | |
| Firefox for Android doesn't natively run userscripts, so you need a manager extension first. | |
| * **Tampermonkey**: The most popular option, officially supported in Firefox for Android version 110 and newer. | |
| * Open Firefox, go to **Menu > Add-ons > Add-ons Manager**. | |
| * Find **Tampermonkey** and tap the **+** (or "Add to Firefox") button to install it. | |
| * **Violentmonkey**: A great open-source alternative that also works well on Android. You can find and install it the same way from the Add-ons Manager. |
Date: 2026-06-12
System: Linux, Cinnamon DE
User: $HOME
| // ==UserScript== | |
| // @name XtoB – Auto Crosspost Twitter/X → Bluesky | |
| // @version 1.6.0 | |
| // @description Auto-crossposts to Bluesky when you POST/REPOST on Twitter/X. Uses author handles (e.g., @user) in reposts. Button mode: butterfly for reposts only. | |
| // @author Mistral AI | |
| // @match https://x.com/* | |
| // @match https://twitter.com/* | |
| // @grant GM_getValue | |
| // @grant GM_setValue | |
| // @grant GM_xmlhttpRequest |
| // ==UserScript== | |
| // @name AO3: Reading Time & Quality Score | |
| // @version 4.0.6 | |
| // @author BlackBatCat | |
| // @description Add reading time, chapter reading time, and quality scores to AO3 works with color coding, score normalization and sorting. | |
| // @match *://archiveofourown.org/ | |
| // @match *://archiveofourown.org/tags/* | |
| // @match *://archiveofourown.org/works* | |
| // @match *://archiveofourown.org/chapters/* | |
| // @match *://archiveofourown.org/users/* |
| --- | |
| name: website-to-epub | |
| description: Convert an mdBook/mkDocs documentation website to EPUB for e-reader reading. Downloads clean Markdown from GitHub source, assembles in chapter order, converts with pandoc. | |
| tags: [epub, pandoc, mdbook, documentation, ebook, converter, website] | |
| trigger: epub documentation website mdbook docs-to-epub convert-docs ebook | |
| --- | |
| # Website Documentation → EPUB | |
| Convert a full mdBook documentation site (or similar static-doc site) into a clean EPUB for offline reading on an e-reader (phone, Kindle, etc.). |
| ## Core Philosophy | |
| 1. **Make complexity the #1 enemy** – Complexity makes code hard to understand or modify. Fight it continuously. | |
| 2. **Strategic over tactical programming** – Don’t just make working code; invest time in good design to reduce long‑term complexity. Avoid being a “tactical tornado”. | |
| 3. **Zero tolerance for complexity** – Complexity accumulates incrementally. Remove it aggressively, even from small changes. | |
| 4. **Design it twice** – Explore at least two radically different designs before choosing one. | |
| 5. **Obviousness is the goal** – Good design makes the system obvious to readers, not just to the author. | |
| 6. **It’s easier to see design problems in someone else’s code** – Use code reviews to gain that perspective. | |
| 7. **If you aren’t improving the design when changing code, you’re probably making it worse** – Always leave the design better than you found it (Boy Scout Rule). |
| **Summary of *A Philosophy of Software Design* by John Ousterhout** | |
| Source: danlebrero.com | |
| These are notes by Daniel Lebrero Berna on John Ousterhout’s *A Philosophy of Software Design.* | |
| Some advice in the book goes against the current software dogma. The current dogma is the result of previous pains, but has now been taken to the extreme, causing new pains. | |
| What the author solves with “Comment-First Development,” others solve with Test-Driven Development. The excuses for not writing comments mirror those for not writing tests. | |
| --- |
| ```javascript | |
| // ==UserScript== | |
| // @name Bluesky Reposts-to-Likes Percentage | |
| // @namespace https://example.com/bsky-repost-like-percentage | |
| // @version 1.0.0 | |
| // @description Show reposts as a percentage of likes on Bluesky (bsky.app) by appending a parenthesized percentage next to the repost count. | |
| // @match https://bsky.app/* | |
| // @grant none | |
| // ==/UserScript== |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.