From 2f7411efe662797357c3535ea6865107da5d9000 Mon Sep 17 00:00:00 2001
From: Baobab <baobab@noreply.codeberg.org>
Date: Wed, 16 Jun 2021 06:12:37 +0200
Subject: [PATCH] add an update to the brave article

---
 articles/brave.html | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/articles/brave.html b/articles/brave.html
index 116b03a..717d299 100644
--- a/articles/brave.html
+++ b/articles/brave.html
@@ -58,6 +58,8 @@
 			<img class="screenshot" src="../images/brave/brave-gstatic.png" alt="google error 404"/>
 			<p>On the first run, Brave fetches five extensions from <code>brave-core-ext.s3.brave.com</code> and tries to install them:</p>
 			<img class="screenshot" src="../images/brave/brave-extensions.png" alt="brave extensions"/>
+			<h3>Quick update</h3>
+			<p>While going through Brave's github repository to explore, I came across a page that details how they handle some of the connections they make.<sup><a href="#ten">[3]</a></sup> As it turns out, they do use google's safebrowsing instead of their own. They do this by proxying the required onnections through their own servers. The same applies to the connection being made to fetch plugin information.</p>
 			<hr></hr>
 			<div class="center">
 				<h4>Sources</h4>
@@ -88,6 +90,9 @@
 				<p><a id="nine">9.</a>
 				<a href="https://static1.brave.com">Brave's static site</a>
 				<a href="https://archive.is/wWgtG">[archive.is]</a></p>
+				<p><a id="ten">10.</a>
+				<a href="https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)">Brave's Deviations from Chromium</a>
+				<a href="https://archive.is/wWgtG">[archive.is]</a></p>
 				<hr></hr>
 				<b>This article was created on 5/7/2018</b><br/>
 				<b>This article was last edited on 12/30/2020</b>