11–20 of 226 posts
Interesting, so would Safari prevent this? I tried moving to Safari and honestly loved everything except I use my google accounts now for authenticating with to many services and that was a pain compared to chrome.
I would imagine using any non-Chromium browser would cause it to fail to find any Chrome extensions, yes.
Interesting, so would Safari prevent this? I tried moving to Safari and honestly loved everything except I use my google accounts now for authenticating with to many services and that was a pain compared to chrome.
as practitioners, where do we hold the line between telemetry and surveillance?
Interesting, so would Safari prevent this? I tried moving to Safari and honestly loved everything except I use my google accounts now for authenticating with to many services and that was a pain compared to chrome.
Well if you’re a logged in to Google don’t you just SSO everywhere?
friends, WHEN you are asked to implement something like this at your job, which will you choose: object (& hold ground, loose job) OR comply (& keep job) as practitioners, where do we hold the line between telemetry and surveillance?
To be clear, LinkedIn shouldn't be scanning your browser extensions, but still. The ultimate problem is that browser extensions are a powerful malware vector and there's a huge market of people buying little utilities off of solo developers to enshittify them.
[dupe] Discussion: https://news.ycombinator.com/item?id=47613981