After opening DU, then opening another tab, then deciding to login, DU, unlike any other site I have used,

[Wonder Why]

doesn't recognize in the second tab that I have logged in.

So, run DU. Not logged in. Open a page in a new tab, not logged in.

Login on yet a third page. Shown as logged in on that tab.

Go back to second or first tab. Click on link to reply to that discussion. Wants me to log in (because it doesn't reread cookies?)

Refreshing the page that failed now shows I am logged in and works fine.

In any other site, If I login on a new tab, the original tab does not show I am logged in but clicking on a link or selecting an option from pull-down menu works because it now shows me logged in on that tab.

Similarly, If I open a tab before logging in, then selecting "Recommend" to post, It takes me to login screen in same tab. If I then login, I am showed that. However, if I backup to the post where I started, then select Recommend, I get

You are already signed in

You cannot sign in because you are already signed in.

Again, I have to refresh that original screen to allow me to continue. So hitting the Recommend button knows I am logged in but thinks I want to login rather than do the Recommend.

I run Firefox on Linux and this has long been a problem. Again, no other site exhibits this behavior except DU. Every other site instantly recognizes the correct current state (that I am logged in) and the step that I want to accomplish. It seems DU is the only one that does not auto-refresh when login status has changed.

[Goonch]

1. ;-{).....

[FakeNoose]

2. There was a DUer several years ago who abused the privilege

It was someone who posted something under one name, and then under a different identity, agreed and supported the views of the first poster. I don't know all the details, but I suspect that things were changed to curtail this type of activity after that DUer was caught.

[EarlG]

3. Unfortunately I was unable to reproduce this just now, at least the first part

In Chrome, I signed out of DU and then opened DU in two tabs, both signed out. I went to a thread in the first tab, then signed into DU in the second tab, then went back to the first tab and clicked reply (without refreshing the page) and it proceeded as if I was signed in, correctly sending me to the reply page.

I then repeated the process in Firefox and got the same result -- after signing into DU in the second tab, the browser recognized that I was signed in on the first tab when I clicked the Reply button, without a page refresh.

That's the way I assumed it would work, so unfortunately I'm not sure why it's not exhibiting the same behavior in your browser. Clearing your DU cookies may help, but beyond that, I'm not sure what the issue could be.

The second problem you describe -- you sign in and then use the Back button to go back to a previous page, then perform an action that requires you to be signed in, and are sent to the sign in page again -- actually sounds like it makes sense, given the first problem. If you are signed out and click the Rec button you will be sent to the sign in page. After you sign in, and then use the Back button to go to back to the thread and click the Rec button again -- without a refresh -- the page is essentially in the same state as it was before you signed in. So you get sent to the sign in page again -- however, once the browser reaches the sign in page, the server recognizes that you are already signed in (because you are already signed in) and so you get the "already signed in" message.

The bottom line is that any time you are signing into DU in one tab and then continuing browsing in another, or any time you sign in and then use the Back button, it could create a problem where the browser doesn't correctly recognize that you're signed in. The simplest solution is to just hit Refresh after you switch to a new tab or use the Back button after signing in, to make sure your browser recognizes that you are already signed in.