These are the reasons I'm stuck on qutebrowser. It's a great browser and project, but I'd love to move away from chromium. If Firefox allowed customizing all these global key bindings I would make the switch.
twirl7303
joined 1 year ago
I'm running roon. It's expensive but self hosted, and has an excellent set of features around a library that seamlessly blends locally stored content with cloud content from either qobuz or tidal. It is great for discovery because I can click into the performers/composers of a track/album and see their other work. Or view a composition itself and see other artists who have performed it.
I wouldn't say it's for everyone but it's been a good fit for me.
I wear one on the subway and it also helps a lot with smells. That "car that smells like shit" is often not noticeable at all.
I use qutebrowser for this reason. Keyboard first controls. All the workaround extensions for Firefox have limitations on about, config, and addon pages. I also had trouble with losing focus to Google docs and when a page is loading. Until Firefox offers full native control options, this was too brittle for me from a keyboard accessibility perspective.
I would love to use Firefox more though once this happens!
If this is not resolved I will likely switch to another service. Free software compatibility was the main reason I paid for bitwarden over its competitors.