Will

Closing because dead

You could probably copy/paste my implementation, or significant portions of it. https://github.com/e-dant/watcher/blob/release/devel/include/detail/wtr/watcher/adapter/linux/fanotify/watch.hpp I'm not aware of any other reasonable implementations on GitHub.

There are a lot of... subtleties with getting fanotify running correctly. I hope there's enough documentation in there that you don't run into them yourself.

> The core::task::Waker type is the common denominator to all interactions with futures, making adjusting its API and implementation especially trying, as it affects the whole ecosystem indiscriminately I'd think...

> Seems to me that linking against fanotify should be sufficient. How do you mean? > That said, if photoprism could be told about added/changed files externally, perhaps an external...

If you're still interested, the `fanotify` adapter on Watcher should be ready soon. It's awaiting some finishing touches [here](https://github.com/e-dant/watcher/blob/next/include/watcher/adapter/linux/fanotify/watch.hpp). I can likely get it into a release this weekend. We...

I may also fiddle with starting up some containers on Windows like so: (From https://docs.photoprism.app/getting-started/docker) ``` docker run -d \ --name photoprism \ --security-opt seccomp=unconfined \ --security-opt apparmor=unconfined \ -p...

(Scala's patterns here seem to be mostly OOP patterns)

I don't have much skin in the game. Wouldn't want your project to take on work that doesn't fit. As for network filesystems -- are NTFS and WSL mounts networked?...

Another thing to note, in re. the fanotify's reporting, is that you can configure fanotify to receive events before or after they occur. I wouldn't say that fanotify's only use-case...