Can't say exactly when the next version will be release (I'll try to relase a minor one in a week or two), but it will include a new attribute on entries that contain the current folder content:

<entry>
    <title>Files in current folder (34)</title>
    <id>293-files</id>
    <updated>2015-03-19T21:52:59+01:00</updated>
    <content type="html"></content>
    <link type="application/atom+xml; profile=opds-catalog; kind=acquisition" rel="subsection"
href="/opds-comics/293/?displayFiles=true" pse:current-folder-content="true"/>
</entry>

Let me know if you want something different.

Like I said in my email, I did not find anything in the logs. Sorry.

I quickly tried Challenger Viewer in folder mode but I was not able to reproduce the problem.
Anyway I would not have been able to do anything as I am not the author of this viewer. You should contact him directly.

Beautiful ! 

Unless Chrome has some sort of auto-refresh mechanism, keeping a tab open on Ubooquity won't do anything as the communication only happens when you are downloading something (the page, a file, an image...).
Once the page is displayed, the server (Ubooquity) does not know anything about the state of your browser.

I'd be interested in seeing the log files of Ubooquity for the period containing the shutdown (as a lot af things are logged when Ubooquity starts and stops).
You can send them to: tom 'at' vaemendis 'dot' net

That's a lot of requests. ;)
Here are my thoughts:

• "cover.jpg": should be easy enough, makes sense -> I'll try to do it
• Title change: will be possible if I decide to use full HTML templates instead of simple CSS themes -> I don't know yet if this will happen.
• Publisher in ComicInfo: it would entail a database structure change and a manfatory full rescan for everybody -> not likely to happen until I have another structure modification to do.
• Subfolders sharings: if you mean sharing subfolders of already shared folders, it won't happen. User access would be a nightmare to manage.
• User quotas: too specific (by that I mean very few people would use it), probably won't do it.
• Server stats: nice but very low priority
• Some stats on web home page: why not.
• Series aggregation on recent additions page: too specific

The CSS you wrote is very likely to be correct, but you can't server custom fonts with Ubooquity 1.7.0.
I'll have to do a few modifications so that Ubooquity can serve font files in additions to the other theme files.

In the meantime, if you want to use custom fonts anyway, you can active the "Raw files" sharing, share your font files this way and include the corresponding URL in your CSS. Quite ugly but it should work.