4 ms·
Some shady stuff going on in an injected browser.js file: https://gist.github.com/xbenjii/2048d8edf135b04790be593ee69ec5e0 https://gist.github.com/xbenjii/2048d
by xbenjii 9y ago
Some shady stuff going on in an injected browser.js file: https://gist.github.com/xbenjii/2048d8edf135b04790be593ee69ec5e0 https://gist.github.com/xbenjii/2048d8edf135b04790be593ee69e...
- Macuyiko 9y agoNot really. All of these are mostly user agent modifications to pretend to be Chrome to make certain sites work, as well as some JavaScript event modification (with a similar purpose). The only "shady" thing is hiding the Chrome ad on Google's home page, though I guess you can consider that as a convenience once you decide to switch fully to another browser. I don't know how easy it would be to pull an update for that file however, in which case it could become shady in an instant.
- neotek 9y agoWhy would they need to update browser.js to do something shady, they can just drop in a brand new binary that does whatever they want it to do and the vast majority of users would be none the wiser.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- neotek 9y agoWhat's shady here?
- zimbatm 9y agoThose look like browser-compatibility fixes, mainly changing the user user agent to chrome on some websites. Or did I miss something?