Atemu

> However, I'm not sure Android actually uses file ctime. It has a creation time in the database that we are using in the app. That database should be the...

AFAICT this only concerns the server. This bug is about mobile.

In fact, as I have written earlier, this bug was already fixed for the server in https://github.com/immich-app/immich/pull/4191. Using the earliest between mtime and ctime is probably a slightly better policy...

> ```nix > exampleArray = [ > "hello" > "beautiful" > ] ++ lib.optionals true [ > "wonderful" > "world" > ]; > ``` This is not legal under RFC166...

> * also weakly violate the standard by not [basing the indentation on the code structure](https://github.com/NixOS/nixfmt/blob/a4639036723e510d8331124c80d9ca14dd7aba02/standard.md?plain=1#L110) I don't find that effect to be weak at all. As mentioned previously, the...

I'm aware there are formatting team meetings and those who are part of the formatting team or just generally interested in the development will regularly be in such meetings of...

I think you're missing the point that most people interested in this particular issue won't be in your regular meetings, no matter how open they are.

> I agree that for lists this is a bullet you can bite, but I don’t know if you can stomach > > ```nix > prePatch = > '' >...

> I do think that both `proposal1` and `proposal2` would thoroughly beat it if you surveyed Nixpkgs contributors. It would have beaten it if you asked just me a year...

Another point to consider is that we often jump more than one upstream release in one update of Nixpkgs. The only possible way to accurately represent that (and unstable versions...