wireguard-install VS chromium

+1 to WireGuard. For people new to it, there are some great scripts which set up and configure it for you like https://github.com/Nyr/wireguard-install

after that u can simply run this script https://github.com/Nyr/wireguard-install that helps you automatically install wireguard and create a config ( to add more configs just run it again ). This script also generates QR code that you can simply scan by ur phone

I currently have WG set up on a Linode Ubuntu server (installed from https://github.com/Nyr/wireguard-install) with Pihole setup in the background. I have everything working just fine, except for some websites showing as "Page cannot be displayed". I've looked up in the subreddit and some have recommended changing the MTU (which I've tried on server/client), but that doesn't resolve the issue. In Pihole, it shows that it responds correctly. I did enable IPv6, but this happened before adding IPv6. Running curl from SSH to access the affected site, it tells me 301 Site moved permanently. Here's the server config:

https://github.com/Nyr/wireguard-install

As for the VPN: I always use this installer on a raspy pi (you can do this on a virtual machine): https://github.com/Nyr/wireguard-install But that is only because I hate having to set up keys.

btw, if you want to speed up the build times you should look to use RE API or Goma. it can make a build finish in about 15 to 30 minutes.

https://chromium.googlesource.com/chromium/src/+/main/docs/l...

It seems like gemini 2.5 is pre-trained on chromium given it has a lot of context into the current state of the codebase. That may help a bit.

Also, I've not tried this yet, but maybe using an MCP server over a clangd language server is a solution to the context problem?

https://chromium.googlesource.com/chromium/src/+/master/docs...

Looks like it's still vendored by Chromium: https://github.com/chromium/chromium/tree/main/third_party/c...

It does happen, but it's pretty rare compared to Windows in my experience, where inconvenience is essentially guaranteed.

Firefox on Linux did not really enjoy being updated while running, as far as I remember; Chrome was fine with it, but only since it does some extra work to bypass the problem via its "zygote process": https://chromium.googlesource.com/chromium/src/+/main/docs/l...

Standard operating procedure for both the Chrome [https://chromium.googlesource.com/chromium/src/+/HEAD/docs/s...] and Firefox [https://www.mozilla.org/en-US/about/governance/policies/secu...] bug tracking systems.

But the fix itself is public in both the Chrome [https://chromium.googlesource.com/chromium/src.git/+/36dbbf3...] and Firefox [https://github.com/mozilla/gecko-dev/commit/ac605820636c3b96...] source repos, and it makes pretty clear what the bug is.

My starting point would be Chromium's documentation, as - presumably - chrome is one of the most widely used and battle tested, user-facing, third party sandboxes running on end user machines.

Windows: https://chromium.googlesource.com/chromium/src/+/main/docs/d...

Linux: https://chromium.googlesource.com/chromium/src/+/main/sandbo...

OS X: https://chromium.googlesource.com/chromium/src/+/main/sandbo...

With the caveat that I wouldn't necessairly assume this is the cutting edge at this point, and there might be other resources to invest in for server-side sandboxing involving containers or hypervisors, and that I've only actually engaged with the Windows APIs based on that reading.

I wrote `firehazard` ( https://docs.rs/firehazard/ , https://github.com/MaulingMonkey/firehazard/tree/master/exam... ) to experiment with wrapping the Windows APIs, document edge cases, etc. - although if the long list of warnings in the readme doesn't scare you away, it'll hopefully at least confirm I hesitate to recommend my own code ;)

It's ok if something doesn't look familiar at the moment. You should google it right away. Or check some source code of v8.

The source is available: https://chromium.googlesource.com/chromium/src/+/refs/tags/1...

It’s not “training an AI model on screen contents without consent.”

It is a stupid feature for Google to enable by default: likely what’s making OP’s machine useless is that it’s running an OCR inference model on the OP’s images to index them for search.

Go to chrome://flags and disable “Enable OCR For Local Image Search” and I bet the problem goes away. The AI Service does have a few other features, but that’s the one that’s likely to be cooking the machine.

As for the other comments on this thread, I doubt there’s anything to do with GDPR here. It’s all local.

The license was explicitly chosen to enable code sharing with LLVM's libc++ (https://devblogs.microsoft.com/cppblog/open-sourcing-msvcs-s...).

The MSVC STL's quality is good enough for thousands of pieces of Windows software (including Windows itself & Microsoft's software such as Office) to depend and rely on. It delivers excellent performance for a broad range of use cases. It is actively developed in the open, delivering cutting-edge (C++23 & C++26) features, accepting Pull Requests and wonderfully documented on GitHub. It can be consumed using MSVC and LLVM clang-cl (which the MSVC STL maintainers test with CI infrastructure). The maintainers are actively working on "hardening" features to enable more secure C++ (https://github.com/microsoft/STL/wiki/STL-Hardening).

Unless you specify what "best" or "a library's quality" means to you, MSVC STL is excellent and because of that, the default choice on & for Windows.

Google chooses to only support libc++ for Chrome/Chromium (https://chromium.googlesource.com/chromium/src/+/main/docs/t...). libc++ is not a Google-owned project.