| 9:07 am on Jul 20, 2001 (gmt 0)|
Not so much the small link but I noticed that once you go to the next page the new indicator disappears so if I don't read for a while I kind of lose where i'm up to past the first page. ( so apologies to anyone if I ever seem to suddenly stop participating in a topic, its usually because of this :) )
| 6:30 pm on Jul 20, 2001 (gmt 0)|
Ok. Added to the list of requests. There have been more requests for the active list than the rest of the board combined.
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.
| 6:32 pm on Jul 20, 2001 (gmt 0)|
Ooooohhhhh......aghhhhhhh....... Exactly what I was looking for.....makes the surfing so much easier for me :) Thanks!
| 6:33 pm on Jul 20, 2001 (gmt 0)|
I am sure that you probably thought of this, but there is no better tieme than this weekend to make the changes you have been waiting to make.......noone will be here
| 6:41 pm on Jul 20, 2001 (gmt 0)|
Jsut another thing that I came across - this is personal perference perhaps. When I make a 2nd post to a discussion where I orignially requested email notification for replies, It's kind of pointless to receive an email stating that I, myself, made a reply to the discussion.
Make sense? Perhaps this could cut down on the number of emails sent out by the system and save you a few $$
| 6:51 pm on Jul 20, 2001 (gmt 0)|
Part of what I am doing today Agerhart - building an archive system for the larger forums.
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.
| 7:05 pm on Jul 20, 2001 (gmt 0)|
Uh... Brett, thanks for the "Next" button in the /active.cgi page :)
| 7:48 pm on Jul 20, 2001 (gmt 0)|
I'll look at the email thing Bradley - I think that is pretty easy.
Good idea! I always thought it was kinda funny to get an email about the post I made two minutes earlier... :)
| 7:49 pm on Jul 20, 2001 (gmt 0)|
Brett, I know its not simple (much easier to find fault than help fix it :) ) - the only thing I can think of is where it shows you all the posts since your last visit on the single page, therefore no extra page loads and no cookie resetting.
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.
| 8:40 pm on Jul 20, 2001 (gmt 0)|
Cookie A, B.
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.
| 9:09 pm on Jul 20, 2001 (gmt 0)|
I just thought of this as well:
" 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.
| 9:51 pm on Jul 20, 2001 (gmt 0)|
Good point Bradley.
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).