It turns out Google Chrome (via Chromium) includes a default extension which makes extra services available to code running on the `*.google.com` domains - tweeted about today [by Luca Casonato](https://twitter.com/lcasdev/status/1810696257137959018), …
hangout_services/thunk.js (via) It turns out Google Chrome (via Chromium) includes a default extension which makes extra services available to code running on the *.google.com domains - tweeted about today by Luca Casonato, but the code has been there in the public repo since October 2013 as far as I can tell.
I am no expert on code-auditing. But I’m slightly at peace that there are 100s of experts looking at the code because it’s open-source. But i also understand mistakes can still happen.
It’s not a perfect system, but it’s the best solution so far.
Remember this thumb rule -> if it’s not open-source, you are allowing the software to do whatever it wants to do.
No regulation, law, support group is going to help you. You are digging your own grave.
I agree, but… This was in open source software. Chromium. Not just Google Chrome. https://github.com/chromium/chromium/commit/422c736b82e7ee763c67109cde700db81ca7b443
https://simonwillison.net/2024/Jul/9/hangout_servicesthunkjs/
If it’s any software you didn’t write yourself or audit every line of…
For a typical Linux distro that’s tens of thousands of packages…
I am no expert on code-auditing. But I’m slightly at peace that there are 100s of experts looking at the code because it’s open-source. But i also understand mistakes can still happen. It’s not a perfect system, but it’s the best solution so far.
There’s some truth to that, but bad actors have managed to slip things through in the past. It happened recently with xz.
I guess my point is that we put a lot of trust in strangers when we run any code on our systems. Open or not.