3 ms·
This title seems a little clickbaity to be honest and I'm not sure how accurate the author's portrayal of Brave's server side is. Based on intuition I imagine t
by i13e 5y ago
This title seems a little clickbaity to be honest and I'm not sure how accurate the author's portrayal of Brave's server side is. Based on intuition I imagine the inability to install extensions has something to do with Chrome's locked down web store forcing Brave to make it's server-side act as a middle man to the chrome web to download and install extensions. Therefore this would be a google/chromium/intentional design flaw and consequence of prioritizing UI/Security over simplicity. If someone understands this better feel free to explain below.
- jonathansampson 5y agoThe problem is definitely a bit more complicated. While it's possible this issue did not involve an issue with Brave at all, it's also possible that it did. The behavior observed (inferring from the screenshot) suggests the user's access to this extension was denied at the time. A 401 response (Unauthorized) from Brave's proxy-endpoint (go-updater.brave.com in this case, I believe) would result in this message being shown. It is entirely possible the user happened to catch a rare, transient issue with our proxy. Sampson (Brave Team) Brave proxies Google endpoints to prevent users from making unintended contact with Google.
- jonathansampson 5y agoResolved: User had a very out-of-date build of Brave. See https://news.ycombinator.com/item?id=29471236 https://news.ycombinator.com/item?id=29471236 for more details.
- i13e 5y agoThanks for the explanation Sampson! I love reading your internals explainers for Brave on HN and I really appreciate how active your team is when it comes to providing information to end users.