migrate to local storage becouse of new limits

[chucem]

chrome has limits on how much and how often data can be stored in sync storage (storage it sync to its cloud service), so we need to migrate settings from sync storage to local storage and remove them from sync storage

• The quota limitation is approximately 100 KB, 8 KB per item.
• 1800 Writes per Hour

wee got a lot of errors MAX_WRITE_OPERATIONS_PER_HOUR and QUOTA_BYTES which broke the background notifications see https://developer.chrome.com/docs/extensions/reference/storage/

possible better solution to sync the settings and not the notification, add listener to sync storage changes and update the local

[what-the-diff[bot]]

PR Summary

• Addition of a New .gitignore Rule The PR introduces a new rule in the .gitignore file that focuses on extension/_metadata/generated_indexed_rulesets/_ruleset1. This change helps to avoid unintentional tracking of unnecessary files in version control.

• Replacing Sync Storage with Local Storage in background.js The developer has made changes in extension/background.js that substitute usage of synchronised storage with local storage in various functions. Details of the affected functions include:

  • chrome.runtime.onInstalled.addListener callback
  • chrome.storage.onChanged.addListener callback
  • debugLog function These changes improve the extension's efficiency by storing extension data locally instead of synchronising it across all the user's logged-in instances of Chrome.

• Updating Storage Methods in background.notifications.js The developer has also replaced synchronised storage methods with local storage methods in extension/background.notifications.js. This shift improves the extension's notifications functionality by efficiently managing notification settings on a local basis.

• Refactoring Storage Usage in settings.js There has been a refactor in extension/js/settings.js where all instances of synchronised storage have been converted to local storage, including getting, setting, and quota specifics like bytes in use and quota bytes per item. These changes pave the way for more efficient handling of extension settings.

• Changing Storage Access in settingsHandler.js In extension/js/settingsHandler.js, access to synchronised storage has been switched to local storage. This change facilitates efficient handling of settings through the settings handler.