Connections to Google
-
*.googleapis.com
*.gvt1.comClean ~ folder, v2.2.1388.37** even forcefully rm'd .config to be sure still those connections are made after a while the browser is running/clicking around in (either) chrome://settings/ and/or chrome://flags/ (obviously no intentionally initiated outgoing connections here)
I am just pointing this out, I would have liked to use Vivaldi but attempting to connect to Google for whatever reason is unacceptable in any case always.
You can't even imagine how much disgusted I am feeling by having to let Cloudflare hijack my connection to post on this forum but that's another point of debate.
At least you aren't fabricating outright lies or trying to sell users browsing history like Brave does so congrats on that.
Mod Edit: Profanity removed.
Mod² Edit: Threads merged. -
@kurikulu Your previous thread had several replies.
-
@Pesala hat thread was 9 months old I assumed the issue to be fixed in a couple days. It really shouldn't take more than a couple of hours in reality; let's even say 3 months if we are having a 3 months long British holiday.
Does it really surprise you then that after 9 months I open another thread to evoke some kind of urgency for such an urgent task that can be fixed in 2 hours instead of 9 months?
Mod Edit: Insulting comment removed.
-
@kurikulu The bug tracker is closed, but you may ask for details on the progress of any bug. The bug number for this one is VB-39696. Use that number when asking.
The right place to ask is in the Bug Status Thread
Be polite. The mods are all volunteers helping you in their free time.
-
@kurikulu Actually, some of those nuisance connections were eliminated back in September and VB-39696 got closed at that time.
As I mentioned earlier in this thread, Vivaldi makes a number of legitimate connections back to Google, e.g. for certificate management. So, even if the Vivaldi team were to eliminate all of those nuisance connections, even though they don't trigger under normal operations and don't send data upstream, it still will not (and cannot) eliminate all connections back to Google.
Edit: The other problem with eliminating every possible connection to Google on every possible codepath is that it would require extensive changes to the Chromium code. This would make code rebases a nightmare (and a nightmare to test) with every Chromium uplift, all for little or no practical gain.
-
I am here to inform myself. I considered a European company to be the first to want to not to support big US-tech companies that circumvent taxes while civilians and small/medium EEA buisnesses pay more taxes than those billion dollar companies. Just imagine Google pays less tax than Vivaldi but still Vivaldi forwards the Vivaldi user as Chrome users. Maybe masochists at work?
possible codepath is that it would require extensive changes to the Chromium code.
extensiveSo what? The changes of code could be done in less than couple workdays if you put someone competent in front of it.
It is not like Chromium tries to hide the connections; I don't remember seeing a SHA encoded base64'd ipv6 address in Chromiums source (this is an obvious joke). And if it really is that hard for someone they can just look at the multiple availible FOSS patches made by private entities that succeed in killing of every single connection.But yea I will stay with Firefox anyway. This is ridicolous how less people actually care about remote connections. A browser that initiates connections on its own without explicit user consent is always bad. And if those connections go to US-Tech giants that browser is the exact definition of malware.
-
@kurikulu Your comments are rather harsh and I think that you misjudge the Vivaldi team -- they really do strive to get rid of as many of these connections back to Google as possible while still keeping the codebase maintainable. And if they can do better, I'm sure that they will.
The ungoogled-chromium project has done some interesting work in this area; so has the Iridium Browser team. You can also uncover a lot of connections just by looking for "destination: GOOGLE_OWNED_SERVICE" in the code so it may be possible to automate much of the work. When Microsoft starts embedding Chromium into Edge, you can be sure that they'll be pushing to make it easy to identify and eliminate these connections as well, so I'm confident that things will get even better in this regard over time.
... and as I've said before, even if you do all of this, you'll still see connections back to Google because they can't be eliminated completely.
In the meantime, all I can say is be patient... and if Firefox is working well for you, then that's great too.