Varun Patil

> That is a correct translation, depending on context. I don't agree, there's no context in Memories where "Surname" would be a valid translation. > I'd suggest defining context also...

This is very nice. Populating the initial data should be easy, just need a loop to copy over during a migration. I'm not aware of any cases where file ownership...

A slightly different implementation is merged (you're co-author!) in https://github.com/pulsejet/memories/commit/eb7fa255b8fb6eb9a774d1b700ff1f5b05929841 Storing the uid in the memories table (and especially the migration) seems somewhat risky. Instead we can directly query the...

Is it currently planned to finish this work? We're using tinygo for wasm because using asyncify is a huge win for optimization and binary size, but the gc bottleneck makes...

This is looking great, thank you for continuing on this! FYI, Microsoft is porting the Typescript compiler to Go and they've explicitly said they might consider tinygo for the wasm...

> @pulsejet > > > We're using tinygo for wasm because using asyncify is a huge win for optimization and binary size, but the gc bottleneck makes it unusable (pauses...

How many photos do you have? What hardware?

15k is very small, memories can easily handle >1M photos. Try the server tuning guide of nextcloud.

https://docs.nextcloud.com/server/latest/admin_manual/installation/server_tuning.html Also you might want to turn on log_bin_trust_function_creators in your database and rerun occ maintenance repair

So I checked on this and it seems to be an upstream limitation. DELETE calls on unassigned faces return a 403. So this will need fixing in [recognize](https://github.com/nextcloud/recognize) first.