Pfah.
Going through and checking changes, I've realized that since we allow tags (
t i
t u
t b
) in taglines, the same fscking can happen there that can happen in posts. Which means that we need to roll the same function against tags as we do posts, which means it's no longer a method of posts, but a generic helper function.
FYI.
it's no longer a method of posts, but a generic helper function.
Does that raise the idea of making QuickEdit available in the tagline box as well, or is that just more trouble and work? Just a thought.
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.
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.