Non shit browser

Like said there really needs to be some l content control system for the user though most of the stuff one would wish for could be solved if qute would add an add-on framework.
What I'd really like to see native is some way to manage more tabs effectively since right now having more than ten will have you switching through them allot.
New Backend when

Yeah - with per-domain settings and github.com/qutebrowser/qutebrowser/issues/2626 it's probably a big step closer to that.

See github.com/qutebrowser/qutebrowser/issues/30 which will be the next big thing to tackle after the new config. Still might take a while, though.

Are you aware of `:set tabs position left` and `:buffer` (gt)?

Many people already use it as their default - and I plan to switch everyone over by default with v1.0 which should happen somewhen later this year.

Firefox or IceCat. Everything else uses either Chromium as a base (so you can be sure there's still some Google shit in the source code somewhere) or WebKit.
WebKit is not very well supported and lacks a lot of HTML5 functionality, so some websites won't look or work well. Most of them have no plugins besides adblocking.
Plus, the lack of support and the weird User Agent makes it easier to fingerprint you.

Firefox or Icecat are the only sane answers.

iridium is pretty comfy

Will you/would you consider maintaining the QtWebkit backend? The QtWebEngine backend is not supported by my device (requires hardware GPU acceleration which I don't have) and renders a black screen.

Does "export LIBGL_ALWAYS_SOFTWARE=1" change anything for you with QtWebEngine?

But yeah, as long as github.com/annulen/webkit/wiki is maintained and PyQt has wrappers for it, I'll continue to maintain it.

They allow you the option of replacing ads with their own ads. The goal is to make it so that users can earn currency by viewing their ads and use that currency to pay sites that they enjoy using. Completely optional, and that isn't the default setting. The default is just blocking the ads. It is chromium based though so if bloat is a concern then this isn't the browser for you. Eich did mention wanting the browser to be privacy focused, so it isn't a terrible option for anyone that doesn't care about bloat.

Good to hear pretty much every point is in the making

Not the buffer command, is there a way to bind it? Tried to do it but it wants the command and arguments without being able to call the list like you can when manually using it through the commandline

There's plenty of non-shit browsers, but the web is too shit for them to be reliable.

It's already bound to gt, but if you want another binding, bind "set-cmd-text -s :buffer" instead. set-cmd-text sets the command line text, and is also used for the o binding, for example. The -s flag adds a space at the end, which needs a flag because of a conjunction of annoying parsing oddities.

~/.config/qutebrowser/keys.conf lets you see the commands that belong to existing bindings.