haha I did not fully. This was also for someone else and a bookmark thing. I do think you can combine it with a backend and get it though that. A rough draft is - front end calls to backend to start oauth. see if that can happen in the window that opens - bsky oauth callback is to the backend
- backend auths user and returns back in that window setting the session (or returns a token for auth to backend). Then you make a call to the backend and it makes the atproto requests. that's a tldr. Going to find an atproto app that does something similar but for mobile and link it
Here's the backend start of oauth building the url github.com/dropanchorap... and this looks to kick it off github.com/dropanchorap...
The auth would be for the browser extension. Maybe I can use @syntacrobat.xyzās cf worker auth
probably so. any mobile workflow should also work for browser extension with the added bonus that I think you can set a cookie that workflow as well so might even make it easier in some ways
Possible +1 reason for an atproto enabled browser, serve auth callbacks for serverless apps? Iām techno babbling out of my ass here.