951 karma · joined November 15, 2016
Disclaimer: I work at Brave
Disclaimer: I work at Brave
Disclaimer: I work at Brave.
Your sentence seems to imply that Cliqz was collecting "[the] data" like American companies (which companies? Which data?). Can you clarify what you are referring to?
Disclaimer: I worked at Cliqz
"Technical difficulties Investigating - We are currently experiencing intermittent network issues affecting some of our users. We are working to fully restore services as soon as possible. We apologize for the inconvenience. Jan 09, 2025 - 16:10 CET"
This seems to impact VPN, Calendar, etc.
May I ask when you switched away from Brave Search? We've been doing work to reduce the amount of captchas a few months ago and we stopped getting feedback about this issue at that point. If it's still happening, it's something we will look into again.
Also, are you a user of ProtonVPN by any chance?
Thanks for your help,
The “augmentation with Google” that you mention is an optional feature that only works in Brave browser and doesn’t mean Brave Search is less independent than in other browsers (but it might mean that the quality is increased for some queries; or at least closer to Google results in these cases).
I think when talking about independence it is important to make a distinction between “dependent” which means “cannot work at all if the provider goes down” (e.g. yesterday’s outage) and “dependent” meaning that the service would continue to operate but with some amount of degradation of service. It’s a spectrum. Yesterday we saw that some services could not operate at all when Bing was down.
Disclaimer: I work at Brave.
Brave Search is fully independent and does not rely on Bing whatsoever so any 500 is unrelated to this incident.
Would you be able to share a query if the 500 happens consistently? We’ll look into it.
Thanks for your help, I hope that helps,
But it definitely still happens now (500s on refresh on PRs and GitHub actions)
Edit: still ongoing
Edit 2: still ongoing at Apr 05, 2024 - 08:56 UTC (keeping updated for the record since their status page cannot be trusted apparently)
Edit 3: I see they have switched to a different (ongoing) incident ID now: https://www.githubstatus.com/incidents/5ly0psff2s5d
I'd like to mention that when you subscribe to Brave Search premium, it is completely decoupled from the searches you then make (no way for us to link your email to your searches) by relying on blinded tokens to prove that you are premium, but without the backend knowing which account (and using one new token per search in order to avoid being able to build search sessions).
I hope that helps,
Are you by any chance using a VPN while using Brave Search? (ProtonVPN?)
Thanks for your help, we're working on ways to reduce the number of captchas shown to VPN users and your feedback is very useful.