|
|
|
|
|
by glenstein
481 days ago
|
|
The same test on my saved articles would show [A] for just about everything. I don't think Pocket ever built itself with intended use cases being such things as looking at tables of server logs showing IP addresses (jimbojones) or Microsoft support pages, and I believe those are probably exactly the instances where switching to a web view exists to account for that. If your deal-breaking use case is that you need an offline only archived web view of Microsoft support for a note about how "OpLock" means the same as "opportunistic lock" I think they're well within their rights to say that that's outside of their intended use cases, and that's what Web View (built into pocket) is for. Certainly room for improvement, but they're just very idiosyncratic use cases. Do you get more success with those same pages on InstaPaper? |
|
This one is a bit silly, I admit, but consider this one:
> Note: Your application should not perform any file system operations on the file between [calling CreateFile2] and [requesting an oplock]. Doing so may cause deadlocks.