Mark Otway

I've just downloaded the image above, but even if I run it through exiftool I can't see any metadata in the image with the word "caption". Are you sure you...

Yes, I just spotted that. Must be having a bad morning. So it seems the library I [use to extra metadata tags](https://github.com/drewnoakes/metadata-extractor-dotnet) can't load the XMP block of data from...

Okay, great. With a bit of luck we'll get a fix (the developer is quite responsive) and then you can just rescan, but hopefully the changes made this week will...

Raised the issue here: https://github.com/drewnoakes/metadata-extractor-dotnet/issues/356

Yeah, that makes sense. I could put the status/work stuff in a different place, potentially. There's also a bug in MudBlazor which means that when the status bar gets updated,...

I use it with qbt in a container on Linux. But I might have auth disabled for simplicity. Will take a look if I have time.

I already do this a bit (if you've read the technical readme you'll see details of how I conflate exif operations to minimise writes to the image files. It would...

Quick bit of googling indicates that it may be this: https://stackoverflow.com/questions/73095624/unable-to-use-azure-face-api-forbidden-error I didn't think I was using any of the gender/facial hair/etc properties, but I'll check and if I am,...

Removed the attributes that MSFT supports - you can try pulling `webreaper/damselfly:dev` and see if it solves the problem once the build finishes in about 15 mins.

Update: the problem appears to be the new policy for Azure Face, which means that only fully vetted Microsoft customers can use the face-recognition features within Azure. https://azure.microsoft.com/en-us/blog/responsible-ai-investments-and-safeguards-for-facial-recognition/?WT.mc_id=AI-MVP-5003365 I have...