Aidan Holm

Seems that way. There are a number of shortcomings with the current WebKit GTK APIs concerning certificates and network handling; for example it is currently impossible to know whether a...

That's a good point. If probing takes too long, then it could be done in a separate invisible webview widget in parallel wth the original request.

There's also https://github.com/luakit/luakit/issues/219 Perhaps we should open a project to consolidate issues about this, or have one mega-issue and close the others? I'm definitely interested in moving towards a more...

It seems that you're mixing the noscript plugin with (domain-specific values of) the `webview.enable_javascript` setting. This won't work currently, as the noscript plugin has its own callbacks that it uses...

Ah, then I misunderstood you; I thought by domain overrides you meant setting domain overrides, not noscript rules. If you're not touching the `webview.enable_javascript` setting at all, then this is...

Thanks for the quick and detailed reply (and sorry for the slow response) > Also, realistically, a good search page needs to be completely asynchronous I'm not sure what you...

> while the search is generating its 100 results, the archiving will stop working Ah yes this is true, but I am less concerned for now, since - archiving requests...

> The server is stateful since archiving -> dump parsing -> indexing is stateful. This is only stateful because the serve path's index is maintained in memory (in the `SortedIndex`)...

> replays have to be synchronous with dumping anyway, otherwise my plans for replay buttons in the extension will break. I'm not sure I If I understand correctly; do you...

> But, as a client, if you dump a new visit for a URL, the server says `200 OK`, and hence you immediately ask for a replay of this same...