I hope that they're not paying "this character" by the hour :giggles:"He's working on it as we speak"
Actually, it can add to SQL queries, sometimes significantly. It all depends on the table and relational design. Each active user likely takes up a record in a table that is used for various serving and, even more so, searches.I don't see the point of closing members accounts because they're not active.
If they're not on the board, then they're not using precious bandwith... it won't make any difference.
If you use Firefox, when you hit "back," it remembers and re-fills your text entries.I'm pretty sure the CEO of freeone's (that was a joke) doesn't do the programming for the website.
it's not that big of a deal, minor inconvenience. except one time when I spent a really long time typing up a thoughtful post and the error popped up and it was lost. that really pissed me off. usually it's after I submit a post and then I notice some error and go to edit it and am unable to do so. that is a bit frustrating as well, because then all I can focus on are the errors that I couldn't correct.
Firefox also does redline spell checking identification, and there is built-in support for correction -- at least it does on Linux where the spell checker is unified for all applications (unified dictionary/thesaurus, user customization which is network-wide if you use network mounts/resources, etc...).That's one of the reason I do my spell checking in a separate word processor. That way in the event something goes wrong I don't lose a long well thought out post. I learned that the hard way.
Bulletin Boards are 100% dynamic content. When they reach the size that FreeOnes has, there are limits without major re-designs.Sometimes I feel like the board is the most overlooked part of the FreeOnes Empire. You wouldn't think they'd let this continue in the "money-making" areas.
The logs themselves will provide extreme more detailed metrics.hope this info helps
Actually, it can add to SQL queries, sometimes significantly. It all depends on the table and relational design. Each active user likely takes up a record in a table that is used for various serving and, even more so, searches.
If you think the problem is just about bandwidth, think again. Dynamic content ain't cheap on memory and I/O.