The code is here if you figure know more about Legend State and can figure out how to do that

github.com/sergiodxa/re...

Here you have, I tried to use the `observe` function but I was not sure how to stop observing the observable once the component is unmounted (the signal does that), the observable onChange works perfectly for this

What is legend state?

Want to dive deeper into how tokens work in OAuth2 + OIDC?

Learn how to use them correctly in your Remix or React Router app.

📘 Join the waitlist for the React Router OAuth2 Handbook:
👉 go.sergiodxa.com/x4HNprT

🪪 The ID Token’s audience is the Client Application.

It contains user identity info and is meant to be consumed by the client, not by the API or auth server. That’s why its aud claim matches the client’s ID.

🔄 The Refresh Token’s audience is the Authorization Server.

It’s the only one allowed to accept it and issue a new Access Token. This keeps refresh logic centralized and secure, preventing misuse by clients or other services.

🔑 The Access Token's audience is the Resource Server.

It’s the one that will validate and accept the token to give access to protected resources. This way, only the Resource Server can rely on it—it’s not meant for the client or the auth server.

ClientLoader doesn’t have access to context, this is a server only thing, rossipedia has been asking for an equivalent client version for a long time

Client side you can define it once in a separate file and just import it

I think @kentcdodds.com build it, he should have the code

On the Remix server we have a bot that can create threads when you add a emoji to a message and automatically name the thread like "🧵 Thread for Dominik"

I use it a lot there to create them so I don’t think about the name

Most of that was already available before the standalone app, although the app is great, would be nice to have secure notes for things like API keys

Yes, you can create a group and share passwords there, you can have many groups too

Does this works with providers like GitHub, Google, Auth0, etc? From what I saw it seems it should since they use client id and client secrets?

I like the ideas it brings, specially ship less JS, but I'm not convinced the complexity is worth it, although I never tried it since I haven't used Next.js in years

I also don't like how it was approached, I always liked that React features were first tested at Meta with their scale, but not RSC

So you can, without Vite 6, already use the actual wrangler instead of the proxy?

I have my own starter github.com/edgefirst-de..., alt ought it does more than just a base point