How LinkedIn exfiltrates extension data from the browser
This is worrying, yet unsurprising. LinkedIn has become a necessary evil for most professionals, unfortunately. The quality of IT opportunities isn't as high as on other smaller job boards in my experience, but I still keep my LinkedIn profile up to date, to get a feel of the market mostly. I look forward to the day I can disable that social network as well.<p>In the meantime, we should build and use simpler web browsers, without extension support for one. I've found surf[0] to be the most usable of all WebKit wrappers. Without much C experience, I've managed to use my own fork[1] for a few months now, which wasn't much work thanks to the lean sub-3KLOC codebase of very readable C code and helpful comments.<p>I imagine that an experienced group of C programmers could take surf as base and easily build a secure and user-friendly web browser with most of the features of the big boys. WebKit is still a concern, but with some work it too could be abstracted away and made easily replaceable.<p>For LinkedIn specifically, I use a separate cookie file, and with the surf process isolation it gives me a degree of sandboxing similar to Chrome. A modern browser should be built on sandboxing principles for web content, and expose this functionality for each site by default.<p>[0]: <a href="https://surf.suckless.org/" rel="nofollow">https://surf.suckless.org/</a><p>[1]: <a href="https://github.com/imiric/surf" rel="nofollow">https://github.com/imiric/surf</a>