The pattern is compared to the whole path of the files and folders.

So if you have a file named ._test in the C:/aaa/bbb/ folder, the pattern has to match C:/aaa/bbb/._test

If you want to ignore all files containing "._", this pattern should work:

.*\._.*

(there is probably a more elegant pattern, I'm not a regex expert)

It wouldn't work with several tabs opened in the same browser on different Ubooquity pages.

The solution you have in mind would not be difficult to implement, agreed, but it still would require time that I prefer to spend on what I call "core" feature of Ubooquity (as opposed to "peripheral" or "nice to have" features).

More explicitly, I am currently working on the online epub reader feature, then I plan on adding server side bookmarks and read/unread status. And after that I'll try to replace the PDF renderer Ubooquity uses for books by the PDF.js library.

I try to estimate what features will be useful to the highest number of people (based on what I read here, and my personal needs) and work on them first.

That's why I was proposing to write a log line (for now), it takes literally 2 minutes to add.

Yep, feature creep. :)

I am not completely opposed to the idea of adding this feature (although if it happens, it'll be in a long time, I have a lot of improvements to make to core features first), but I still fail to understand how it is different from downloading the epub file then sending it by email.

A few less clicks, granted, but is this an operation you'd perform so many times it would be worth the cost of implementation ?

That's something I already tried to implement in the very early versions of Ubooquity.

I gave up because it would have added a bit of complexity to the paging mechanism (the solution I tried involved keeping the folder navigation history somewhere) and because I found the "back" button of the browser to be sufficient to go back where you were before.

In what kind of situation is the "back" button of your browser not enough ?

And just to be sure, do you know you can click on the page number to display a "go to..." menu ?

I might have an idea to implement that without keeping a navigation history (which I won't do), but it might have an impact on performances. So I have to do some tests first.

This would be nice indeed, but with my backlog of features growing faster than I can implement them, it'll have to wait a bit. ;)

What I can easily do, if you think you can exploit it, is generating a log line with scan results each time a scan is done. You could quite easily get statistics using a few shell commands.

What do you think ?

Yes I'm good now, thanks. :)

Hi,

you're right, the problem exists on all versions of Safari (iOS and OS X).

I tried a few things in my code, but to no avail.

The only advice I can give to work around this:

• use HTTPS: I read somewhere that Safari was not using HTTP pipelining (the root cause of the problem) in HTTPS mode
• configure Ubooquity to display less images per page: from what I read, the problem happens more often when pages contain a lot of images
• Use another browser, Safari is the only browser having these kind of problems with HTTP pipelining, all others work fine

I'll add it to my todo list.

Dont expect it soon though.