"new posts" rollover

[Nicholas A. A. E.]

This is kinda annoying for me to leave a few dozen threads unread and then come back in the morning and see that the system has decided to stop flagging them unread. Apparently there is a time limit after when the system thinks I don't want to read old posts anymore.

This doesn't happen to me on other vBulletin forums (or at least, the deadline is much longer, e.g. 7 days). Makes me think there's a setting I'm missing somewhere. Can anyone help out?

 

[Claverhouse]

This is probably a sad function of the Session Timeout global setting, which is based on cookie management.

Here, due to Ragnar's admirable modesty, the timeout --- which is the stated time since a user's last action ( merely refreshing a page even ), and before the user must re-login [ obviously not a factor noticed by those who have the little fox recall all passwords and transparently log in ] --- is set at 7500 seconds, which as far as I recall his saying was the closest he could get to 2 hours in an aesthetically desirable round number.

Why so low, when many boards set it at 24 hours or longer ? His reasoning was that as the number of people online reported on the main page is based on the Timeout Session, people still within being counted present although they might have left many hours before, this artificially inflated the numbers and was essentially Living a Lie. Lying may be permissible sometimes, ethicists struggle with that one, but boasting, exaggerating, and feeling good about oneself, is disgusting.



It is a pity that the two issues are not separate, as they should be, but that's vBull for you. It is actually entirely possible to switch over to Server Management instead of Cookie Management which solves many problems; however this is implemented with an appalling feature which ensures that once the user has read the thread, it is removed from the entire list of New Posts...

People Online is further complicated not only by it's giving different numbers on the Front Page, on the Who's Online page, and serverside, but by a hack installed --- again to keep the actual number truthful --- which on Who's Online alone cuts down guest visits to those active in the last few minutes. The high numbers of people online on nearly all internet boards is due to bots and devices touching base from a second to a minute, then leaving, but being continued to be reported as a guest until their session timeout runs out.

Many admins like and desire artificially inflated numbers to boost their board's reputation and their own frail egos. We here, thank God, are wholly free from the Sin of Pride and utterly scorn our rivals' inadequacies.




Claverhouse

 

[Cogwulf]

Many admins like and desire artificially inflated numbers to boost their board's reputation and their own frail egos. We here, thank God, are wholly free from the Sin of Pride and utterly scorn our rivals' inadequacies.

Who needs pride when you're better than everyone else

 

[Nicholas A. A. E.]

It is a pity that the two issues are not separate, as they should be, but that's vBull for you. It is actually entirely possible to switch over to Server Management instead of Cookie Management which solves many problems; however this is implemented with an appalling feature which ensures that once the user has read the thread, it is removed from the entire list of New Posts...

I'd prefer that, I think. What good is it having a bunch of read threads, even if they are new?

I've actually started clicking "Mark all forums read" after I finish reading everything, so all the "new but read threads" are cleared from the list and I don't run into this problem I get where the system suddenly makes me log in to the forum again, and 100% of the "new" threads are again considered unread. Even the ones where I'm the only new poster.

As long as I'm complaining about this stuff, it happens often (about 10% of the time) that I'll read a thread but it'll still be considered unread. I'll have to click on it once or twice more to get the reading registered. The page is fully downloaded and rendered each time.