Also, let's think of a better word then "Threadsuck". "Download", perhaps? "Archive"? "Save"?
'Potential'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
I like "Threadsuck", but I can see that we might not want the string "suck" to be on a page for filtering reasons. Download would work for me.
I think if suck breaks a filter, we've broken the filter. There're worse words in just about every page.
Still, not attached to the term at all.
Wow, I'm amazed that worked the first time, ita.
Anyone else who needs access to the CVS repository, please send me mail at the profile address. I'm at my in-laws place this weekend, and all I have is dial-up, so I'll check mail but I won't be on the board much.
I just think the term would add a touch of vulgarity to an otherwise clean design. Plus, forget looking it up in a dictionary to figure out what it means, if English isn't your first language.
If it comes to that, I believe you should be able to just ask someone, Rob. You can't look up "meara" or "Nilly" or "xpost" in a dictionary, either.
I like "threadsuck".
Wrod.
None of the words you mention are part of the user-interface for the board, so I wouldn't apply as high standards for choosing them.
I think we should try to choose words for the interface that don't require a new user to ask what they mean.
Oh, c'mon, it's no more anti-intuitive than the way we use "tagline". And, eventually, we'll have a MARCIE. People are going to have to find out what that means, too.
This is the internet. There are going to be neologisms. "Threadsuck" is a perfectly good term. And if your opposition to it is based on the grounds that a word with "suck" imbedded in it isn't going to be workplace-friendly-- dude, if it's not huge text or in the title bar of your window (as a title of a thread would be), and it's only *imbedded* in the word, I really can't entirely be swayed by that argument.
I think it hurts usability. Browser based interfaces start off at a disadvantage, since they usually don't have things like tooltips or context sensitive help. Picking code-words for the "buttons" just seems to make the board it harder to use.
I'll be arguing against using "MARCIE" anywhere in the user-interface, too, if it comes to it.