pull down to refresh
Thanks for the report!
So basically the session needs updating on nym change?
Yes. Or better: we should use user ids.
Yea, I didn’t want to refactor it to use IDs when I originally implemented the privacy feature, just to keep the changes smaller. But using IDs would have prevented this. However, it still surfaced a bug that needs fixing
No worries, fix is simple :)
I still think we should update the session on nym change too, even though this change fixes the bookmark issue
That would be ideal, yes
But I have the feeling it's not going to be simple. We would have to reissue a JWT which is handled by next-auth. Can we issue a new JWT without the need for reauthentication? Should we even be able to do that?
Good catch!
Yay! Happy to have helped!
Have you changed your nym without logging out and back in? That could be a reason that your session still thinks you're your old nym but the database already uses the new nym.
That would indeed be a bug!