Christopher Johnstone

Thanks for the work so far on this issue. Here's another datapoint on possible weird bit-depth formats that comes up in some of the microscopy data we handle. The instrument...

> > I can upload one of these images if it is helpful. > > Please do. `.tif` isn't an allowable upload so here's a `.zip` of a `.tif` [asymmetric_bit_depth.zip](https://github.com/python-pillow/Pillow/files/9285976/asymmetric_bit_depth.zip)

To add some detail to this since my users are seeing this: The problem is specifically with direct Facebook chats. If I (facebook ID AAAAA) message another Matrix user (facebook...

I have the same issue on Windows; I'll possibly try to dig around with a debugger in the C part of the library at some point later this week, and...

I'm working on an update for #1287 now, looking at how the code has been reorged.

@kradalby, do you want me to open a new PR or reopen the earlier one? A fix for this is freshly rebased after the code reorganization and is reasonably ready...

I'll poke around the current auth code, but I think right now there isn't an assumption of a unique user identifier claim in Headscale. Perhaps there's a nice way to...

I'm considering implementing something similar to Matrix Authentication Service's user attribute mapping, which would make it generalizable: https://matrix-org.github.io/matrix-authentication-service/setup/sso.html#user-attributes-mapping

Looks like the combo of subject and issuer claims are unique: https://openid.net/specs/openid-connect-core-1_0.html#ClaimStability Maybe I'll update the PR to use this combo internally. That would be a pretty annoying UX though...

Is there plans to reintroduce this and/or is there something that I could contribute to to help? I couldn't find an issue in this repo regarding CI, if that is...