grenzbotin / eco2rd Goto Github PK

Goal

• Update the GHG data to the most current available.
• Add more country data (GHG/kwH): 🇦🇺 Australia, 🇦🇷 Argentina, 🇧🇷 Brazil, 🇨🇦 Canada, 🇮🇳 India, 🇮🇩 Indonesia, 🇯🇵 Japan, 🇲🇽 Mexico, 🇷🇺 Russia, 🇸🇦 Saudi-Arabia, 🇿🇦 South Africa, 🇰🇷 South Korea, 🇹🇷 Turkey

** Goal **
In order to better understand the size of the visited site it could be helpful to categorise the initial load size into a score equivalent to see how much data is loaded with the (last) initial page load.

Potential scale (in g CO2):
0 - 0.5g dark green
0.5g - 1g light green
1g-2g yellow
2g - 4g orange
4g+ red

Wanted behaviour
The installed version number should be shown in the pop up (e.g. via settings).

Additional Information
With every version update, the version numbers need to be increased in /public/manifest.json + package.json, too. The same number is expected to appear in the popup.

Manifest v3 is not supported by Firefox, yet.
According to Mozilla, they plan to support it from early 2022 on.
https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/

** Goal **
Adapt the potentially needed changes in background.js and test accordingly for making the extension available in Firefox.

In order to develop flawlessly, the plan is to create proper pipelines for

• Development
• Production

Currently, whenever you want to run the extension in unpacked mode, it looks the same as in production. This makes development slightly unhandy. The plan is to amend a dev tag in e.g. manifest.json if the dev run the command yarn build-dev in order to be able to distinguish dev mode from prod mode.

Additionally it makes sense to right away change versions if a production build was created. This can be then used for sourcing the right number in #2, too.

Bug description
When the user is not active with the browser but still consuming media (via e.g. stream) the data collection stops at some point. Thus, the numbers visible to the user are stopping increasing, too.

Additional information
Likely the behaviour is related to an unexpected behaviour of the manifest v3 service worker:
The service worker from Manifest v3 seems to be shut down automatically after 5 minutes.
This does not appear to be an issue if the user is constantly moving in between tabs and actively browsing.

More about it can be found here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1152255#c25

Expected behaviour
The service worker, and therefore the data collection shut not stop if the user is passively consuming data via e.g. media streaming.

In order to make the extension broadly accepted and used, we could introduce localisation that will support different languages.

** Feature description **

• Set browser language as language in extension automatically
• Fallback: English
• Create folder with localisation files
• Setup i18next
• Add a dropdown in settings that show all languages
• Ensure that number & date formats are shown correctly

Nice to have:

• Find people to translate into their mother tongue

Cons
The extension size will get larger due to localisation files.

What to do
In order to be accurate with the latest numbers, update the related gCO2 / kWh used in the calculations.

Potential source
https://www.climate-transparency.org/g20-climate-performance/g20report2021#1531904804037-423d5c88-a7a7

Don't forget to update the readme accordingly.

In order to be able to compare different months and years, it would be nice to replace the current "total" scope with a view that enables the user to easily compare different months in terms of data transfer (green vs. grey, electricity & co2eq).

Goal: Update the countries' power mix while keeping historical values into account.

A year flews by and there are new country based power mix numbers that need to be taken into consideration. As historical values got introduced in one of the recent versions, a power mix update should take it into consideration.

Link to climate transparency report: https://www.climate-transparency.org/g20-climate-performance/g20report2022#1531904804037-423d5c88-a7a7