Change forum marking please?

[TonyB]

Can we change this to #3 Instead of the brain-dead #1? It is the most usable method for users, and I can't believe HG is short of CPU. Currently, when I click an email notice of a response, the forum starts a timer and by the time I get back in the evening to read New Posts it tells me there aren't any! Very frustrating.
TIA

Thread/Forum Read Marking Type
This option controls how threads and forums are marked as read. The options are:

1) Inactivity/Cookie Based - once a user has been inactive for a certain amount of time (the value of the cookie timeout option) all threads and forums are considered read. Individual threads are marked as read within a session via cookies. This option is how all versions of vBulletin before 3.5 functioned.
2) Database (no automatic forum marking) - this option uses the database to store thread and forum read times. This allows accurate read markers to be kept indefinitely. However, in order for a forum to be marked read when all threads are read, the user must view the list of threads for that forum. This option is more space and processor intensive than inactivity-based marking.
3) Database (automatic forum marking) - this option is the same as a previous option, but forums are automatically marked as read when the last new thread is read. This is the most usable option for end users, but most processor intensive.

[striddy]

Originally Posted by TonyB

Can we change this to #3

Sounds like a good suggestion.

[gwyneth]

I agree, and while you're at it, did someone change the "Home" in the gray nav bar up top to forums.hostgator.com?

What I'm getting at is, didn't it used to go to "Home" on the Host Gator site instead of "Home" for forums? With everything else in that gray nav bar referring to the rest of the HG site, it might make more sense for "Home" to, as well.

[TonyB]

I dunno. Today it's pointing to http://www.hostgator.com/ , as is the logo.

[kmaw]

Originally Posted by striddy

Sounds like a good suggestion.

I agree. They must be worried about cpu usage with the db.

[TonyB]

I doubt they would notice any great cpu usage increase. I suspect this setting was simply made in error. Especially since nobody has come on to say otherwise.