Current state of per-domain settings

Since I've been asked for the current state of per-domain various times, here's a quick overview:

History

I've planned to implement this as part of the recent crowdfunding, but things have taken a bit longer than expected there (and I like doing things properly rather than doing more but half-baked). See these two blog posts (especially the last sections) for more context. Because of that, I haven't been able to work on this full-time like I originally wanted.

Current status

There's some thoughts on how this affects various parts of qutebrowser, but there's no code yet.

However, the requirements to get started on this (the new config) are finally out of the way, even though it took almost three years because I was mostly busy with tests and QtWebEngine stuff before starting work on the new config.

What I'm busy with

Currently, there's a couple things keeping me busy:

  • My studies (and other real-life stuff). This will always have priority over qutebrowser work, and the workload is a lot bigger than I anticipated, as there's a lot of project work I need to do during the semester (something like 13 projects, compared to 2 or so last semester) to be allowed for the exams.
  • Taking care of the T-Shirts and other rewards (other than stickers) for the crowdfunding. I postponed this during the full-time work so I could finish the new config, but this takes a lot more time than one might imagine.
  • Taking care of contributions - a lot of nice contributions (such as GreaseMonkey support) are currently in the pipeline, but taking care of reviewing those and "mentoring" people also takes a fair amount of time.
  • "Support" - meaning everything related to helping in people in the IRC channel, Reddit, private mails, issues on GitHub, etc. It might not seem like much, but it's easily an hour or so per week as well. It's not something I want to do less off though, as I think it's very important (and it's also a nice break from all the coding and writing I'm doing for my studies).

In the time remaining for qutebrowser work after that, I really don't have the time nor mental energy to work on something big like this I'm afraid. If I push code changes to qutebrowser myself lately, it's either some important bug fixes, or just something I felt like would be fun for once again.

Future

So, as you can imagine, I can't really give you an ETA for this (and I've historically never done so for work I do in my free time, because I just end up making false promises anyways).

In ~Febuary, I have two weeks of holidays after exams, and I might be able to tackle this then. I might be able to look at (the basics of) it before that, when I feel like I need a break from other coding and can work on something bigger again. Or it might need to wait longer, because those are holidays after all, and after three weeks of writing exams, maybe I'll just need a break for once.

I can imagine some people aren't really happy with this situation, and I'm not really either (I still really want NoScript/uMatrix-like functionality myself!). But that's just how things turned out I'm afraid. I did what I could during the crowdfunded time.

All posts

  1. qutebrowser v1.0.0 released!
  2. qutebrowser v1.0.0 is coming closer
  3. New config merged!
  4. Config revolution - Part 1 finished
  5. Refactoring more things, a working YAML config, and more!
  6. Refactoring all the things!
  7. First week
  8. First 2 days
  9. Getting started again
  10. Second qutebrowser crowdfunding launched!
  11. qutebrowser v0.10.0 released
  12. Wrapping up and looking at the future
  13. Days 39/40/41: Lots of features!
  14. Days 37/38: Hints in master, tests
  15. Day 36: Hints!
  16. Days 33-35: Mouse functionality, and rewriting hints
  17. Days 31/32: More web elements
  18. Days 29/30: Web elements
  19. Days 27/28: Settings and web inspector
  20. Day 24-26: Refactoring the WebElement API
  21. Day 21-23: After Europython and releases
  22. Day 19/20: Bugs everywhere!
  23. qutebrowser v0.8.0 released
  24. Day 18: Javascript
  25. Day 17: Printing and searching
  26. Sending out qutebrowser and pytest stickers
  27. Day 15/16: Merged!
  28. Day 13/14: Almost merged!
  29. Day 12: Tests running!
  30. Day 10/11: Refactoring!
  31. Day 9: A bit of everything
  32. Day 8: More fixing and pytest sprint/training
  33. Day 7: Fixing things
  34. Day 6: Branching off
  35. qutebrowser v0.7.0 released
  36. Day 4: Playing whack-a-mole
  37. Day 3: Last pull requests and managing requirement files
  38. Day 2: More pull requests and nicer test output
  39. Day 1: Merging pull requests, and a stupid bug
  40. About and Timeline