Now that we're able to auth into the site, we should add the ability to persist user preferences.
Basically, anything in the settings page should be stored server-side (likely in the KV store) bound to the user's unique ID.
This doesn't need to touch atproto, it just needs to privately store the data and associated ID.
Now that we're able to auth into the site, we should add the ability to persist user preferences.
Basically, anything in the settings page should be stored server-side (likely in the KV store) bound to the user's unique ID.
This doesn't need to touch atproto, it just needs to privately store the data and associated ID.