3 ms·
If you like vimium, or the idea of it, consider giving qutebrowser a spin. Chrome hampers extensions in a variety of ways (e.g., not being able to use vimium bi
by hansvm 2y ago
If you like vimium, or the idea of it, consider giving qutebrowser a spin. Chrome hampers extensions in a variety of ways (e.g., not being able to use vimium bindings on any "internal" pages), and a fully fledged browser makes the experience much more cohesive.
- yasser_kaddoura 2y agoYou can extend Qutebrowser with userscripts [1]. For the Lisp fans, Nyxt [2] is a decent choice as well. [1] https://qutebrowser.org/doc/userscripts.html https://qutebrowser.org/doc/userscripts.html [2] https://nyxt.atlas.engineer/ https://nyxt.atlas.engineer/
- yashasolutions 2y agonyxt would be awesome when it has a decent browser engine. For now you cannot use nyxt on most regular websites (youtube is broken most of the time), They are working on moving it to chromium engine if I understood correctly. But yeah when it will be ready, it's the browser I waiting for the most.
- kataklasm 2y agoi used QB for years and loved it but eventually i couldn't stand not having uBlock Origin anymore.. shame there's not a good adblocker for QB
- mariusor 2y agoI'm pretty sure they have an adblocker in Qutebrowser. It might need some additional dependencies installed.
- griffzhowl 2y agoNo. 8 in the faqs: "Is there an ad blocker? Since version 2.0.0, if the Python adblock library is available, it will be used to integrate Brave’s Rust adblocker library for improved adblocking, based on ABP-like filter lists (such as EasyList). If that library is unavailable or on older versions of qutebrowser, a simpler built-in ad blocker is used instead. It takes /etc/hosts-like lists and thus is only able to block entire hosts. Note that even the more sophisticated blocker does not support element hiding (cosmetic filtering) yet, it only blocks network requests." So depends on what one means by "good adblocker"... https://qutebrowser.org/doc/faq.html https://qutebrowser.org/doc/faq.html