Tracking which threads you have already read

[Svpernova09]

That sounds about right for how it's done, Nova.

Problem with the cookie thing is it mainly just keeps track of website visiting activity, and not thread visiting activity. So you can visit the site, and after a bit, it'll mark all forums as read, based upon the time stamp of the cookie. Even if you never visited any of those threads.

I can understand the rationale behind it from a programming standpoint, as it's a lot easier than keeping individual database track records of when things were visited and such. But in the end, I know I at least feel it's kinda nice knowing that something is going to remain unread until I either click into the thread to read it, or click on some button that says "Mark (sub)forum as read".

Either way, it's not a huge deal, as I'd much rather have the forums up than down. But I can totally see where the frustration is coming from.

Yah, I see where people are coming from. I'm not trying to just flat out say "No I won't change this" but the problem is, if I do change it, it will have very adverse effects on the site's overall performance. And I'd rather be able to have the site run speedy for everyone.

[Ridere]

Yah, I see where people are coming from. I'm not trying to just flat out say "No I won't change this" but the problem is, if I do change it, it will have very adverse effects on the site's overall performance. And I'd rather be able to have the site run speedy for everyone.

I totally understand. And that's why I'm glad you're managing the system and not me. I've done my share of website support and application support and such. It's so much easier to just be a user and not have to worry about actually maintaining anything.

I used to write legitimate proxies/bots for another game (Well, moreso just a graphical chatroom with minor RP elements, hence why bots would be legitimate), and I'm glad that I don't deal much with that anymore.

[Owltoid]

Yah, I see where people are coming from. I'm not trying to just flat out say "No I won't change this" but the problem is, if I do change it, it will have very adverse effects on the site's overall performance. And I'd rather be able to have the site run speedy for everyone.

Are you sure it will make a noticeable impact on performance? I agree if the site becomes sluggish then the current functionality would be preferable, but it's possible that we can't notice the slowdown if it's slight.