I'd rather take out the tag-ability and put quickedit in. Limited quickedit, though.
Or we could just not have HTML in tags. I'm good with that too.
'Lineage'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
I'd rather take out the tag-ability and put quickedit in. Limited quickedit, though.
Or we could just not have HTML in tags. I'm good with that too.
Hokay. Implemented some of Jon's changes -- you are now informed (via a server-side count) that your tag has been amputated. Also put in the screen so one can change the number of posts displayed.
Oooh, spanks!
ita, since we're worried about bandwidth issues, which is preferable -- more posts/page or fewer?
It won't make any difference to the bandwidth if you read 100 posts in ten lots of ten or five lots of twenty -- it'll just make the pages larger for your browser.
Really? I would have thought that 10 separate hits would require more. But I know nothing about this.
OK I take it all back. I answered without thinking.
I'd delete my post, but that would be cheating.
The answer to Jessica's question is, less bandwidth gets used up if you have more posts to a page.
This is because the page consists of both posts and furniture, nav, forms, graphics and whatever.
So five lots of twenty is five lots of furniture and ten lots of ten is ten lots of furniture.
If you only downloaded the posts, it would all be equal.
less bandwidth gets used up if you have more posts to a page.
Excellent.
As my penance, I did the maths -- here's a randomly chosen full page of Natter (as in, not at the end yet, somewhere in the middle):
Total Posts Furniture 18.3 Kb 8.7 Kb 9.6 Kb
So that page, which has, let me see, ten posts, is about 47% content and 53% furniture.
If it had twenty posts, let's just make up a figure:
Total Posts Furniture 27 Kb 17.4 Kb 9.6 Kb
it would be 64% content. Someone check my calculations?
This is ignoring images, which is OK because they're few, and they're cached.
[edit because numbers are meaningless if you don't know what they're enumerating...]
Okay, this has got to be the coolest feature EVER!!!! Because, like, there doesn't seem to be a limit to the number of posts that can be displayed. It's like an automatic threadsucker!!!
Okay, taking a breath...
The bandwidth downside is that if you set the number of posts fairly high, and click onto a thread that you've already read to the end, you'll get the last however many posts you set instead of just the last ten. I don't see that as much of a problem though, and it is a great feature for folks trying to catch up.