Just using up-to-date Chrome. I see the network request where I get redirected to "https://digs.fm/users/auth/spotify/callback" with a code and state. It returns a `Set-Cookie`, but I see my next request to the digs.fm homepage has another `Set-Cookie`. Unsure if you are just re-generating session IDs on every request or if the session data from the callback is being overwritten when I hit the homepage again.

I have the same issue. Firefox, Windows 10; also Firefox, macOS.

I don't see myself in the New Users list on the main page. Perhaps it's completing the authorization on Spotify's end, but not creating the user account on the Digs end?

Sorry for that, I found the root cause, unfortunately it'll be a bit before that's fixed, I guess (depends on action on behalf of Spotify).

Might it be something to do with how your account is registered with Spotify? Mine was signed up for with Facebook (ugh) and I'm seeing that bug.