Oauth works partially in the tauri window, but should be opened in the user's browser instead.

Most of this works already, but we'd need to modify the redirectUri to get back a token from the user's authorization server. Two ways to do this are deep linking and a temp redirect server.

Deep-linking: Requires some json to be stored server-side, like what oauth-client does. But AFAIU, atproto's oauth spec allows a different scheme for native redirectUri's (com.example.app:/callback) from tauri (<scheme>://url). So we'd need to route this to the roomy web version, like /oauth/callback-native which would actually trigger the deeplink.

Redirect server: Spawns a server to handle the callback. Would need to change how atproto.init() works because the server's port is not known until the auth process has started (technically could use a static port number, but everything would fail if it's already in use).

I put the client metadata for tauri in static/oauth-client-native.json so it gets bundled into tauri's binary. Tradeoff is that the domain is fixed across dev.roomy.chat and roomy.chat. Deep links from either url work, so it could be fetched/changed dynamically. Not sure if there's anything showing up in the app to use as a condition for that.

tradeoff is that domain fixed to across dev.roomy.chat and roomy.chat.

That sounds good for now. 👌

Don't worry about fixing / debugging the issue with the @automerge/automerge import because we're migrating to Loro very soon.

Is there anything else outstanding to do on this?

Is there anything else outstanding to do on this?

@zicklag Just the key setup for android, but that isn't something I can do on my end. I haven't done any tests with beyond signing in because of the Automerge issue. Other than that should be ready to go.

Merging it will break the rest of the app though because the automerge imports are commented out. I could undo that in the PR and leave a note for anyone trying to test it out

Just the key setup for android, but that isn't something I can do on my end.

That's fine, we can do that once we're ready to publish to android.

Merging it will break the rest of the app though because the automerge imports are commented out. I could undo that in the PR and leave a note for anyone trying to test it out

Ah, yeah, that sounds good. 👍

❌ Deploy Preview for roomy-dev failed.