Contributing

Testing

You can help us by logging any issues you find. As a small team, prioritization is critical, so knowing which issues are impactful for many users can help us with that prioritization.

Spread the word

You can help by telling your friends, or discussing our features in a forum or on reddit, twitter, quora, etc. You can write a blog post or make YouTube video. If you do, then send a link to our email, and we will publish it too.

We need documentation,

.gifs /screenshots /videos, Content for Tooltips, Tags & alternative names of the features (for search, multi-language)

Translation

You can help us to translate ImprovedTube into your language. Please, check the wiki page.

Donate

We are volunteers. ImprovedTube is made out of love for our users. Your happiness is the currency of our hearts. We dare to keep ImprovedTube open-source & free, despite it is still a lot of work, that won't stop while YouTube releases updates.

• Bitcoin: 144kqL6nGEQtVL3QCdADY4EtduZ95Vu1pL
• Ethereum: 0xf6E03Ffa6B04c972C45c91D6Bc449Be81E1C527c
• Stellar: GC25BRDKV5HIJX4IZJXFNKG5PWEPZX56NZKTDJ5YCR4O6YY7Y3M2JL65
• BitcoinCash: qqseudey582dz72l23nspw0ch8ezlgty25jpqjdkun

---

Development

• Bugs, ordered by activity (also linked in readme.md#to-do + precisely: wiki/todo )

  • Advanced: label:important & Pinned issues (meaningful).
    • Feature Requests (especially: #Set-and-forget, #Plan, #Unique, #Should be crowdsourced, ... )

• Use our locale.py to add / change the human language in the extension

  • Updating the name or value of a feature of option in our menu? ‐ Import people's old storage!

• We have some global variables & regex

• We observe the DOM for changes to apply features as soon as certain elements appear

• We have our extension popup's GUI & re-purposable functions in our little library Satus.js

• We react to settings changing immediately, so that we can call the feature before the next page-reload (or possibly an introductiory animation, or undoing a feature that's switched off)

Dev. Convenience / Efficiency / Methods

• Testing Browser-Extension changes with 1 click: Extension Reloader & enable the option to reload the current tab too & set a nice shortcut like alt+E chrome://extensions/shortcuts
  

  • Alternatively fully automatic: https://github.com/rubenspgcavalcante/webpack-extension-reloader

• Build script (old)

  • • store APIs / github actions/workflows + auto testing #842

• Depending what feature you work on : https://github.com/kdzwinel/DOMListenerExtension, https://chrome.google.com/webstore/detail/visual-css-editor/cibffnhhlfippmhdmdkcfecncoaegdkh, https://chrome.google.com/webstore/detail/editthiscookie/fngmhnnpilhplaeedifhccceomclgfbg

• Q: "Youtube runs up to 3 GUI versions at once, depending what account i use..."

  • A: "They might only test changes could be permanent."
    • Remedy: we always have the option to sensitively offer GUI on top of Youtube, instead of fiddling to integrate our's: CSS position:fixed or sticky)

---

• Debate: Predicting Youtube-DOM changes?

  The important CSS IDs (& pathes) _should_ stay the same in all current & future YouTube.
  Yet, we _could_ predict how Youtube might be renaming some still... An Extension could even search for new names if old ones disappear. More over, regEx can be cheap & even CSS allows some wildcards / 'regular expressions' *= ^= $=
  
  • An editor to compare 3 Versions: Download (Alternatives@Wikipedia)
    (Some YouTube versions: archive.org/2021/youtube, 2020, 2019)
    

---

GitHub in general:

• Pull Requests by command-line: gh pr create --base master --title "my PR" --body "fixing..."
  - Alternatively: hub pull-request acts as a wrapper for git) https://github.com/github/hub - (Or if you hate all Pull Requests, we might allow you to make commits after a few PRs)