Comment by dotty-

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.