Merge branch 'Anarios:main' into main

2 files changed, 8 insertions, 8 deletions

diff --git a/SECURITY-FAQ.md b/SECURITY-FAQ.md
index 5f52904..a8e27fc 100644
--- a/SECURITY-FAQ.md
+++ b/SECURITY-FAQ.md
@@ -6,7 +6,7 @@ No. The extension's code is public and you can see it for yourself. The only inf
 
 ### Can you uniquely identify me if I dislike?
 
-Yes. When you dislike a video, we create a randomly generated unique ID for you that is not tied to your Google account. This is done to prevent botting.
+Yes. When you dislike a video, we create a randomly generated unique ID for you that is not tied to your Google account. This is done to prevent botting. But there is no way to tie this random Id to you or your personal youtube account.
 
 ### What information do you have, exactly?
 
@@ -14,7 +14,7 @@ Just the video ID. Not your comments, not your username, not who you've shared t
 
 ### How is my IP stored?
 
-The backend keeps IP addresses in volatile memory (RAM) only. These addresses aren't stored on a hard drive, and therefore aren't logged. We hash the IP addresses, and that's stored instead. This is done to prevent database vandalism.
+The backend keeps unhashed IP addresses in volatile memory (RAM) only. These addresses aren't stored on a hard drive, and therefore aren't logged. We hash the IP addresses, and that's stored instead. This is done to prevent database vandalism.
 
 ### I heard some discussion over OAuth, and access to my YouTube account!
 
@@ -26,5 +26,5 @@ We have implemented measures to prevent bot attacks and are gonna continue to wo
 
 ### Why don't you share the backend code? 
 
-We may share it at some point - but there's really no real reason to share it. It gives a false sense of security - because in a zero-trust system, we could just as well disclose one version but deploy another. There are plenty of reasons to keep the code hidden, specifically, how we battle spam. Hiding/Obfuscating the spam handling code is a fairly standard practice.
+We will share it at some point - but there's really no real reason to share it right now. It gives a false sense of security - because in a zero-trust system, we could just as well disclose one version but deploy another. There are plenty of reasons to keep the code hidden, specifically, how we battle spam. Hiding/Obfuscating the spam handling code is a fairly standard practice.
 
diff --git a/Website/pages/faq.vue b/Website/pages/faq.vue
index 71d2080..9ce4693 100644
--- a/Website/pages/faq.vue
+++ b/Website/pages/faq.vue
@@ -36,23 +36,23 @@ export default {
       {
         question: "Where does the extension get its data?",
         answer:
-          "A combination of Google's API data and scraped data. We save all available data to our DB so it can be made available after Google removes dislike counts from their API.",
+          "A combination of archived data from before the offical YouTube dislike API shut down, and extrapolated extension user behavior.",
       },
       {
         question: "Why isn't the dislike count updating?",
         answer:
-          "Right now video dislikes are cached and they aren't updated very frequently. Currently this is set to update once every 2–3 days.  This isn't ideal and we are working on improving how often we can update them.",
+          "Right now video dislikes are cached and they aren't updated very frequently. It varies on video popularity but can take anywhere between a few hours and a few days days to update.",
       },
       {
         question: "How does this work?",
         answer:
-          "The extension collects the video ID of the video you are watching, fetches the dislike (and other fields like views, likes etc) using our API, if this is the first time the video was fetched by our API, it will use the YouTube API to get the data, then store it in the database for caching (cached for around 2-3 days) and archiving purposes, and returns it to you. The extension then displays the dislike count and ratio on the page.",
+          "The extension collects the video ID of the video you are watching, fetches the dislike (and other fields like views, likes etc) using our API. The extension then displays the dislike count and ratio on the page. If you dislike or like a video, that is recorded and sent to the database so an accurate dislike count can be extrapolated.",
       },
       {
         question:
-          "What will happen after the YouTube API stops returning the dislike count?",
+        "Can I share my dislke count with you?",
         answer:
-          "The backend will switch to using a combination of archived dislike stats, estimates extrapolated from extension user data, and estimates based on view/like ratios for videos whose dislikes weren't archived as well as outdated dislike count archives.",
+          "Coming soon. We are looking into using Oauth or a different read only API with a limited scope so creators can share their dislike counts verifiability. ",
       },
     ],
   }),