3 ms·
> We face a number of challenges simply letting our paying customers change their search engine: I use Kagi's extensions to maintain Kagi as default search acr
by WarOnPrivacy 2y ago
> We face a number of challenges simply letting our paying customers change their search engine:
I use Kagi's extensions to maintain Kagi as default search across many devices and browsers. It's been seamless across Firefox/Waterfox/etc instances.
IIRC, Kiwi and Brave were fairly agreeable (I avoid Chrome, Edge). Opera was a pain because Opera is a pain about everything.
I appreciate the effort you+team have put into this.
- prophesi 2y agoI did have issues on Linux regarding the extension working in private windows due to the official Firefox extension being out-of-date. Using the latest Github release of their extension fixed it, and they promptly submitted the new update for it to propagate through the extension store after a ticket on their feedback forum asked about it[0]. Github releases with .xpi's to install have been removed[1] which is odd but hopefully they keep up with their Firefox extension submissions if this is the route they're going down. As for Chrome, I only use it for automated/manual testing since that's what everyone uses. [0] https://kagifeedback.org/d/2234-kagi-extension-api-key-not-persistent-in-firefox-esr-on-kali-linux/25 https://kagifeedback.org/d/2234-kagi-extension-api-key-not-p... [1] https://github.com/kagisearch/browser_extensions/releases https://github.com/kagisearch/browser_extensions/releases
- hugh_kagi 2y agoWe're definitely keeping the extensions going, just need to prioritise a few parts internally. You can just git clone the new chrome extension and 'load unpacked' if that's of any use. It's extremely simple. https://github.com/kagisearch/chrome_extension_basic https://github.com/kagisearch/chrome_extension_basic
- prophesi 2y agoAny advice to Firefox users who want to do the same? I don't use Chrome or its derivatives.