From c70441dabf50d42624cef5a06128377c4938c3c2 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 6 May 2023 15:33:02 -0400 Subject: [PATCH] reformat Vanadium default connections --- static/faq.html | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/static/faq.html b/static/faq.html index af7d2119f..8979f8afc 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1016,23 +1016,27 @@

What kind of connections do the OS and bundle

DNS resolution for other connections involving connections to the network / user provided DNS resolvers

+
  • +

    Vanadium, our browser and WebView implementation, uses + update.vanadium.app to check for updates to components + providing revoked certificates and other data. It downloads the + components from dl.vanadium.app.

    +
  • +

    Other Vanadium browser connections are initiated by the user such as the + search engine (defaults to DuckDuckGo), websites and retrieving favicons for + your bookmarks and the frequent sites shown on the home page. We enable + connection and cache partitioning to keep connections separate between + different sites. There are a few parts of state partitioning still being + implemented including cookie partitioning which is currently in the testing + phase but causes too many compatibility issues to fully deploy it by default + without any exceptions like Brave's heuristics to disable it for cross-site + login flows, etc.

    +

    Unlike Chrome/Chromium, Vanadium WebView does not make connections beyond those initiated by the app using it so there are no default connections from apps using the WebView.

    - -

    Vanadium browser uses update.vanadium.app to check for updates - to components providing revoked certificates and other data. It downloads the - components from dl.vanadium.app. Other connections are initiated - by the user such as the search engine (defaults to DuckDuckGo), websites and - retrieving favicons for your bookmarks and the frequent sites shown on the - home page. We enable connection and cache partitioning to keep connections - separate between different sites. There are a few parts of state partitioning - still being implemented including cookie partitioning which is currently in - the testing phase but causes too many compatibility issues to fully deploy it - by default without any exceptions like Brave's heuristics to disable it for - cross-site login flows, etc.