Posts by quentin@piaille.fr
(DIR) Post #Azdj7gGfOkd39gEAlc by quentin@piaille.fr
2025-10-27T09:25:35Z
0 likes, 0 repeats
@dos @bart Hey! I'm the developer who introduced OAuth in Matrix. Getting the redirect back to native client is a very complex topic, and also highly dependant on how the native app is being shipped.This is especially a problem on Linux where Element doesn't maintain the many of the packages themselves, plus the many ways to run it (Flatpak, snaps, community repos), so we have no guarantee that the custom scheme handler is correctly installed.When I implemented the redirect back to the client, I foolishly assumed that a HTTP redirect to the native scheme was enough; which was the most convenient way to have the whole flow JS-free
(DIR) Post #Azdj7hKbRbN6SB4pXc by quentin@piaille.fr
2025-10-27T09:30:09Z
0 likes, 0 repeats
@dos @bart I'm looking for a few ways to improve the flow in those edge cases. One way is to consider the Device Code Grant (https://github.com/matrix-org/matrix-spec-proposals/pull/4341) in cases where we're not sure the redirect will work.Another thing is to give a nice proper link to users to get back to their client instead of relying on an HTTP redirect that can't be replayed. The suggestion to give out the code to copy back to the client as a last resort is interesting, even though ideally we should really not need those kind of potentially confusing workaround :(
(DIR) Post #Azdj7iJvlaQbWNlo8G by quentin@piaille.fr
2025-10-27T09:36:31Z
0 likes, 0 repeats
@dos @bart I know this is probably not the answer you would like to hear (nor one I'm really happy giving) but part of the truth is, we're really resource constrained, and sometime cannot afford spending resources to fix problems that don't affect customers paying us (this one mostly affects Linux users on community packages). It's on my personal list of 'things to do/fix when I have spare time', but that list is long and spare time is not something I have much of :)