Feature-Request: Less connections to googles servers

[JoachimHenze]

OS: WinXP SP3 32 bit
Supermium version: Supermium 122.0.6261.85 Hotfix (R2) 32bit https://github.com/win32ss/supermium/releases/tag/v122-hf
A feature-request with just LowPriority (fixing the handle-leaks and improving youtube performance is more important than this ticket)

I have set up the browser to show about:blank on startup via #custom-ntp

Still whenever I do start the browser it does a lot of network connections TCP and UDP to some google servers (original Chrome does that too).

The request is to minimize those network connections for this about:blank usecase.
I would be fine with using additional cmd-line flags for that purpose.

Here is what the browser currently connects to when just opening it with about:blank:

I am rather sure that the 8.8.8.8 connections are rather innocent (as that is one of googles DNS server).
But I do hope that some of the other connections could be avoided.

[docrR]

Many flags have been added from Ungoogled Chromium, with more planned in the future.

[JoachimHenze]

fae3961
and
e9ead93
and
53dfbe3
are related and were committed after "Supermium 122.0.6261.85 Hotfix (R2)" was released already, so I will retest with this flag on the successor version. And see whether things will have improved then or not.

[win32ss]

Unfortunately, it is only incremental. The changes did not stomp out all the connections in my testing, so I will go further before releasing Supermium 122.0.6261.152.

[JoachimHenze]

Thank you very much for your outstanding perserverance!

[JoachimHenze]

I retested "Supermium 122.0.6261.152 (R4)".
When I had the flag --ungoogled-supermium enabled, I could no longer play videos on youtube.
And still not all connections during startup were suppressed.

I decided therefore to stick with the stock setting for now.

[JoachimHenze]

I retested "Supermium 124.0.6367.245 x32 on XPSP3x86" with cmdline --ungoogled-supermium and

• yes, the situation improved. I can now access youtube even when the flag is set
• yes, the amount of connections during initial startup with about:blank as new-tab-page decreased with this version

But, still not perfect, 2 remaining problems:

• 1.) it still opens one undesired connection initially to 34.206.39.153:80
  
  I looked up that host:
  

• 2.) when I enter something into the omnibox which is not an URL, it does no longer perform a google-search for that. Some people might actually prefer it that way, but it would be nice if it was configurable via a subparameter that the omnibox-google-search would still work

It's pretty close to being a good compromise now already, I will work like that for a few more days to see whether I will find any other flaws.