AgreeableLandscape@lemmy.ml to Privacy@lemmy.ml · 2 years agoWhy DuckDuckGo Is Attacking Google Over Its Privacy Promiseswww.makeuseof.comexternal-linkmessage-square6fedilinkarrow-up115arrow-down10file-textcross-posted to: digitslfreedom@exploding-heads.com
arrow-up115arrow-down1external-linkWhy DuckDuckGo Is Attacking Google Over Its Privacy Promiseswww.makeuseof.comAgreeableLandscape@lemmy.ml to Privacy@lemmy.ml · 2 years agomessage-square6fedilinkfile-textcross-posted to: digitslfreedom@exploding-heads.com
minus-squareSr Estegosaurio@lemmy.mllinkfedilinkarrow-up2·2 years agoHardened Ficefox and a locally selfhosted SearX instance. 🧐
minus-squareXpeeN@lemmy.mllinkfedilinkarrow-up2·edit-22 years agoBut the default behaviour of self hosted searx is to expose the server’s IP to the actual search engines, do you use VPN or something at the server side?
minus-squareSudoDnfDashY@lemmy.mllinkfedilinkarrow-up2·2 years agoHardened Ungoogled Chromium and a self hosted SearX instance for me!
Firefox+SearX is the answer.
Hardened Ficefox and a locally selfhosted SearX instance. 🧐
But the default behaviour of self hosted searx is to expose the server’s IP to the actual search engines, do you use VPN or something at the server side?
Hardened Ungoogled Chromium and a self hosted SearX instance for me!