Support for wtm.page messages

Author: philipp-classen

extension-manifest-v3/src/background/reporting/index.js

@@ -89,6 +89,8 @@ const config = {
     COLLECTOR_DIRECT_URL,
     COLLECTOR_PROXY_URL,
     CONFIG_URL: 'https://api.ghostery.net/api/v1/config',
+    SAFE_QUORUM_CONFIG_ENDPOINT:
+      'https://safe-browsing-quorum.privacy.ghostery.net/config',
     ...platformSpecificSettings(),
   },
   request: {
@@ -107,6 +109,7 @@ const communication = new AnonymousCommunication({
 const urlReporter = new UrlReporter({
   config: config.url,
   storage: new Storage('reporting'),
+  connectDatabase: prefixedIndexedDBKeyValueStore('reporting'),
   communication,
 });
 let requestReporter = null;
@@ -176,10 +179,6 @@ const setup = asyncSetup([
   }),
 ]);
 
-function delay(timeInMs) {
-  return new Promise((resolve) => setTimeout(resolve, timeInMs));
-}
-
 async function onLocationChange(details) {
   try {
     setup.pending && (await setup.pending);
@@ -220,15 +219,7 @@ async function onLocationChange(details) {
   }
 
   try {
-    const jobRegistered = await urlReporter.analyzeUrl(url);
-    if (jobRegistered) {
-      // TODO: This part here is not robust:
-      // we should avoid timers in MV3 or at least assume that we the service
-      // worker will die (persisting the jobs and shift the scheduling
-      // responsibility into the reporting module itself could help)
-      await delay(2000 + 3000 * Math.random());
-      await urlReporter.processPendingJobs();
-    }
+    await urlReporter.analyzeUrl(url);
   } catch (e) {
     console.warn('Unexpected error in reporting module:', e);
   }
@@ -253,12 +244,13 @@ chrome.runtime.onMessage.addListener((msg, sender) => {
   }
 });
 
-// for debugging service-workers (TODO: provide a way to control logging)
+// for debugging service-workers
 globalThis.ghostery = globalThis.ghostery || {};
 globalThis.ghostery.WTM = {
   communication,
   urlReporter,
   requestReporter,
   config,
   webRequestPipeline,
+  extensionStartedAt: new Date(),
 };