And proud of it.

I'm assuming that if no one sticks up for a modification, it can be taken off the list.

DX -- if posts don't stretch the screens out, is there anything else manual that needs be done to prep threads for archiving besides zipping the threadsuck? Of course, there's no way to really automate it if we can't zip in PHP (anyone know if we can find a module?), but I want to make sure we're making it as simple a manual process as possible.

Add character count to text over posting box

I'm not sure this is necessary now that we have the automatic post continuation.

Perhaps we should have an "Aussie counter" (or a "Backward Antipodean Counter") somewhere on the site so people don't have to keep asking.

Was this to determine what was NADFA-safe? Don't think that's relevant any more.

Wait, we have to stick up for ones we want? I vote for these:

• Ability to label bookmarks
• "Subscribe to this thread" link in thread header
• List of threads in "set profile" be the other way around (ie, last first)
• Pictures, either with every post or just in the profiles (I would vote for in profiles)
• Jump to date in thread
• tagline archival
• "unmark" link for bookmarks on the actual post page, instead of "marked".

Wait, we have to stick up for ones we want?

I think that's the safest way to get rid of stuff no one actually cares about -- I'd like to hear what to delete and why, and what to keep and maybe why if it's not obvious.

Me, I think these are unneeded:

• CVS repository
• Add character count to text over posting box
• Option not to show taglines
• User set style: font, colour, etc (covers for visually impaired, dislike of fonts, size, and several others)
• List of threads in ?set profile? be the other way around (ie, last first)
• Threads arranged by type (NAFDA, spoiler, etc.) see BbaBB 2521 for Nou?s suggestions.
• Force Beep Me and Press to the top of Message Center
• work-friendly (distinctive logo/graphics only on the front page, not when reading posts)
• Pictures, either with every post or just in the profiles
• message system, by which private posts can be left for other member, of limited length and retained for limited duration
• tagline archival
• (optional) birthdates in user profiles, with automatic "Happy Birthday to []" displays
• Events -- give users the ability to enter an event (JM playing guitar, ASH on Leno) which will be displayed up to the relevant date
• Perhaps we should have an "Aussie counter" (or a "Backward Antipodean Counter") somewhere on the site so people don't have to keep asking.
• "we're loading over a thousand user names into the combo box every time we want to edit a title"

I'd want to have better specs on:

• Searching user list by e-mail address (I'm not down with a searchable user list, honestly, although I know it's a pain)
• Quickedits for tiny text, line break [BR], and links (we have tiny (coming up) and links. Do we need the line break?
• More tags: BLOCKQUOTE, TT, SUB, SUP, CENTER, S (for strike) (we have strike and a c quickedit)
• problem with quotes in taglines (not sure what this is about)
• Add First Book and heifer.org to Links page as preferred charities (can be done by anyone, if the categoty exists)
• Full-screen, large font compose box for impaired vision. (maybe a impaired vision style sheet?)

Can we enforce a rule where ita can't post in lightbulbs accidentally, thus scaring the crap out of me?

So you don't want stuff I stuck up for. Now what?

Seconded

So you don't want stuff I stuck up for. Now what?

Either elimination or prioritising via bullshit consensus, I'd think.

Or I win, and go post ALL OVER LIGHTBULBS with whatever I want.

DX -- if posts don't stretch the screens out, is there anything else manual that needs be done to prep threads for archiving besides zipping the threadsuck? Of course, there's no way to really automate it if we can't zip in PHP (anyone know if we can find a module?), but I want to make sure we're making it as simple a manual process as possible.

That's pretty much it. It got a lot easier when I decided to make the minimum assumed screen resolution 800 x 600 instead of 640 x 480. The [link] thing will make it way easier. The only thing left that I can think of that I've seen as problems are really-massively-hyphenated-words-and-phrases, and stuff in <pre> tags. Also, the <pre> tag still doesn't do line spacing quite right in Mozilla/Firefox. You get a ton of extra lines between paragraphs.

Should I make a request for making sure one quotes the correct post to respond to? ;-)