Unread post limit
12-02-2011, 03:00 AM
#2
Moderator
Joined APC: May 2006
Position: ATP, CFI etc.
Posts: 6,056
A pc geek can correct me, but I think these are the main reasons.
*the IB software logs you off after about ten minutes of inactivity. The APC browsing history then unlinks you from the user name and links to the IP address you were on (I think). Since reading a thread page can easily take more than ten minutes we tend to get logged off and our browsing trail disassociated. This occurs even more when we change IPs frequently (travel).
*cookies may enter the equation as well, but browser behavior varies. Could be anything from no cookies, dispose of only when shutting down, dispose of when closing the browser, quite a few possibilities. Look into that.
*the IB software logs you off after about ten minutes of inactivity. The APC browsing history then unlinks you from the user name and links to the IP address you were on (I think). Since reading a thread page can easily take more than ten minutes we tend to get logged off and our browsing trail disassociated. This occurs even more when we change IPs frequently (travel).
*cookies may enter the equation as well, but browser behavior varies. Could be anything from no cookies, dispose of only when shutting down, dispose of when closing the browser, quite a few possibilities. Look into that.
12-02-2011, 05:46 AM
#3
Gets Weekends Off
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
Cub -
I didn't understand a thing that you said in that reply
, but I'll give you an example of what I thought he was trying to get across.
In the thread 'Need some advice" I read all the way to post #21 last night.
This morning I get on the site, hit new posts, see the same thread, open 'Need some advice", and then click on 'View first unread'
In my mind, this would take me to the first post after the one that I read last night (#22).
But it didn't. It took me directly to post #24. I only realized that I was missing something when the 'first' post reference something that I knew I hadn't read before - thus making me look back and seeing that there were posts # 22 and 23 that were skipped.
USMCFLYR
I didn't understand a thing that you said in that reply
, but I'll give you an example of what I thought he was trying to get across.In the thread 'Need some advice" I read all the way to post #21 last night.
This morning I get on the site, hit new posts, see the same thread, open 'Need some advice", and then click on 'View first unread'
In my mind, this would take me to the first post after the one that I read last night (#22).
But it didn't. It took me directly to post #24. I only realized that I was missing something when the 'first' post reference something that I knew I hadn't read before - thus making me look back and seeing that there were posts # 22 and 23 that were skipped.
USMCFLYR
12-02-2011, 09:15 AM
#4
Gets Weekends Off
Joined APC: Mar 2011
Posts: 180
I'm guessing that this is because the software can only detect when you click on things, not what you actually read. For example, if you open a thread today, and it has 25 total posts, and you only read up to post #20, the system can't tell that you didn't read post #21. So tomorrow when you log in, it's just going to show you the thread as it appears tomorrow (say, with 30 total posts), because it's working off of the state of the thread based on when clicking on threads happen.
12-02-2011, 09:18 AM
#5
Gets Weekends Off
Joined APC: Mar 2011
Posts: 180
Originally Posted by Cubdriver
*the IB software logs you off after about ten minutes of inactivity. The APC browsing history then unlinks you from the user name and links to the IP address you were on (I think). Since reading a thread page can easily take more than ten minutes we tend to get logged off and our browsing trail disassociated. This occurs even more when we change IPs frequently (travel).
12-02-2011, 10:27 AM
#6
Gets Weekends Off
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
Originally Posted by CleeIB
I'm guessing that this is because the software can only detect when you click on things, not what you actually read. For example, if you open a thread today, and it has 25 total posts, and you only read up to post #20, the system can't tell that you didn't read post #21. So tomorrow when you log in, it's just going to show you the thread as it appears tomorrow (say, with 30 total posts), because it's working off of the state of the thread based on when clicking on threads happen.
I wouldn't expect the software to know that I didn't read all of the current posts - but read my scenario again.
I had read all the way to the end of the thread the first time. When I came back - it seems the software assumed that I had read posts #22 and #23 and started with number #24, when the last time I clicked on the thread there were only #21 posts.
USMCFLYR
12-02-2011, 11:54 AM
#7
Moderator
Joined APC: May 2006
Position: ATP, CFI etc.
Posts: 6,056
CleeIB answered in the time it took me to write a response. I sit here at my desk and write a post sometimes, then get interrupted, and come back hours later to finish it...
Last edited by Cubdriver; 12-02-2011 at 12:07 PM.
12-03-2011, 07:26 AM
#8
Gets Weekends Off
Thread Starter
Joined APC: Dec 2007
Position: Fixed wing, left
Posts: 434
That explains it. Too bad there isn't a way for the system to recognize what I actually have scrolled over and read. Google reader does this with blogs I follow which I have found to be helpful. On that very long Delta thread, it's hard to trace back to where I have left off.
12-03-2011, 09:55 AM
#9
Gets Weekends Off
Joined APC: Sep 2008
Position: F-16
Posts: 185
Mind/Forum interface
Originally Posted by Scooter2525
That explains it. Too bad there isn't a way for the system to recognize what I actually have scrolled over and read. Google reader does this with blogs I follow which I have found to be helpful. On that very long Delta thread, it's hard to trace back to where I have left off.
John
Thread
Thread Starter
Forum
Replies
Last Post
