Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: lawman
I'm going to offer up a 2 cent suggestion. I'm always viewing the most active posts when I visit WebmasterWorld.....When I go here: [webmasterworld.com...] and then I want to read the next list of active discussions, there isn't a nice big "NEXT" button......Instead, I have to click on the small numbers located on the right hand side.
Think you could add a "NEXT" button at the bottom that would allow a person to see the next set of posts.....
Does anyone agree / disagree with me on this? Am I the voice of many, or the voice of one ? :)
The tough part for me, is that the page gets viewed so much (sometimes as high as 15k per day), that I'm resistent to changing much on it.
I updated it a little - not much - but a little.
Make sense? Perhaps this could cut down on the number of emails sent out by the system and save you a few $$
TPK, that's a tough one with the last read pointer there. I'm not sure where to go with that, or how to solve the dilemma. Currently, that page has a cookie on it that sets the last time you viewed it - then you reload the page and it resets the cookie. That's pretty clean and easy for the regulars. Any suggestions?
I'll look at the email thing Bradley - I think that is pretty easy. I'm also in the process of switching the email from "email on post" to an email cron job every 15minutes. That should cut down on dupe posts as the system seems to "freeze" when it runs into a email address that bounces or takes to long to process. As it is now, it sends out the email from the time you press submit until it comes back.
Of course, doing that adds extra problems I guess - you would have to put a cutoff on the length in case someone doesnt view for a week etc..
I wouldnt worry about it too much, I will just try to rely on my faulty memory - I only brought it up because I saw the thread.
User visits a page w/ No cookies. A and B get set to the current date/time.
User visits a page with cookies: If cookie B was set within the last X minutes, cookie B is updated with current date/time. If cookie B was not set within the last X minutes, cookie A gets the value currently in cookie B, cookie B gets current date/time.
New posts scripts use cookie A to determine which posts are new.
I think that would work. 15+ would be a good number for X, to protect against a user reading a thread for a long time.
" I'm also in the process of switching the email from "email on post" to an email cron job every 15minutes."
If this is the case, just send one email listing the 10 people that have replied to the post within the 15 minutes, instead of sending 10 emails that each list one person.
I can't say I like getting flooded with emails when they all point to the same discussion.
Interesting idea ggrot. Hmmm. I will give that some thought. In the mean time, I have this cooking on the back burner:
Every message gets a serial number. Not just the thread (as it is now), but every message.
You get a cookie "last message read: #serial number".
The system easily knows from a list, just how many messages you haven't read.
A new option at the top of the screen would show up "read new" that would take you to the lowest message number.
At the bottom of the thread would be a link "Read Next New" that would take you to the next new message flatout.
I could also do just "read next" when could take you to the next message in sequence.
The tricky part I'm laboring with, is when to update that last read serial cookie? Do it manually like we do now, or something else. I can't store a "read flag" for every post (whew, that would chew some disk space).