about all the changes...

[Drew4UTk]

apologies for putting y'all through this.  

sometime back i ran into a bug and couldn't figure it out for the life of me, so, i adjusted what it impacted instead... well... i found the bug, and now i'm going back through fixing the fixes.  

at the same time, though, i'm revisiting some of the things you guys have asked for such as having the 'post' bar below the post as well as on top... I had to read that request like three times to grasp what was being asked, but i finally figured it out... "some posts are long, and scrolling back up to hit reply or quote is a PITA"... so... it's on the bottom now, too.  there are a few more things i'll straighten out too before this is over with, but it's getting closer to being done than it is just starting.  

[DunkingDan]

I like the way New use to appear
The READ that shows on threads to me is distracting 
I wish there was a way to be able to see thread views like we use to on the original A51, it was easier to see who was responding to who
Lots of times when clicking on a topic I get told I am forbidden to see it 

[Drew4UTk]

aye- I can easily hide the 'read' thing. 

i can also dress up the thread view some.  it's actually on my list of things to do... i was waiting for a new js.library that will make the posting formatting more proper instead of the crazy way the current library does it (and which i can't manipulate)....

the forbidden thing is important! thank you for mentioning it.... i see it from time to time too, and here is what i think is going on with that:

• it happens when you click to a page before a page is completely done loading, and the 'sessions' validation hasn't completed- verifying you can see what you are asking to see... 

my solution to this problem is coming... i MADE this problem, inadvertently, when i laid the horsepower to the server... it loads too fast (under a second and a half most the time for the DOM, and under three completely)... the sessions script doesn't run until last, so... i'm going to make it run first- but that means the page will load a split second more... it's better than getting the 403 forbidden, though, so that's what's going to happen.