Consistency in naming

In creating user documentation and site copy, we want to ensure that we have consistent naming, rather than calling things one thing in one place, and something else in another. Here are things that could potentially have multiple names, where we need to pick just one and stick to it.

Please add to this page with any other things you can think of where we need to stick to just one name.

Userpics/icons
I'm not sure which of these is in more widespread use. I think I see "icons" more, but I don't really pay much attention to the things so I'm not a good judge. What do people think?

I think that Userpics is a LJ Support-based thing. Icons, I feel, has a wider usage. John 22:47, 11 January 2009 (UTC)

Syndicated accounts/feeds
I'd propose using feeds where possible, and "feed account" where we need to differentiate between the account that gets created on site, and the actual source RSS/atom feed.

+1. John 22:47, 11 January 2009 (UTC)

Archive/Calendar
Calendar better describes (a) the general appearance, and (b) the function. Archive makes it sound like there's a distinction between old, archived entries, and more recent ones (or like the user has to do something to distinguish archived entries from normal entries, as though it were a 'favorites' thing). --Isabeau 23:59, 11 January 2009 (UTC)

Voice Post/Phone Post
Won't be an issue when the site launches, since we won't have it (I believe), but we may as well figure out what we're going to call it when/if we do.

I vote for Phone Post, only because that then leaves open the possibility of a record-straight-to-post function in the event that technology mashes together once everybody and their dog has a mike on their computer. John 22:47, 11 January 2009 (UTC)

Profile/User Info
I think I like profile best. --Foxfirefey 22:21, 11 January 2009 (UTC)

Ditto. If it hadn't started life as userinfo.bml then I'd never think of it as the userinfo page. John 22:47, 11 January 2009 (UTC)

Calling it profile might also make it more consistent with other blogging platforms and therefore easier to navigate? Forthwritten 23:17, 11 January 2009 (UTC)

Friends Group/Filter
I like Filter because of the WTF system - calling it a Friends Group might be confusing if you're filtering a watch list Forthwritten 23:20, 11 January 2009 (UTC)

I think we needs two types of filter - watch filters and trust filters. The two are used for different things, and it would be nice to have them be different entities. You wouldn't even need to have the 64-bit limit on watch filters since the 64-bit value only applies to trust-filtering a post. --Sophie 00:54, 12 January 2009 (UTC)

"Reading filter" and "trust group" perhaps? Going with different names might help limit possible confusion, maybe? Rho 03:19, 12 January 2009 (UTC)
 * I think it would make more sense the other way round, because most people use the term "filtered" to mean filtering their posts. So "Trust filter" and "reading group" might be better. --Sophie 11:55, 12 January 2009 (UTC)
 * 'Trust' might be a bit of a loaded term. Perhaps calling it a "content filter" is more neutral? 79.75.2.80 13:09, 12 January 2009 (UTC)

Help/Support?
Maybe not an actual one, but "Help" links to the Support area.

I don't think there's anything necessarily wrong with that. John 22:47, 11 January 2009 (UTC)

Layout/Style/Theme
These do refer to different things, but people have a hard time keeping track.

For those who aren't aware what the terms currently mean on LJ with regards to S2: A style is composed of different layers. The most important is a "layout" layer and has the main information. A "theme" layer has minor differences, and a layout can have several different themes to choose from.

But yes, most people use the words interchangeably. I don't have any suggestions for different names, though. --Sophie 11:59, 12 January 2009 (UTC)

Post/Update/Entry
Entry vs. post -- entry is the verb, post is the noun. Thus, should not use update. Update.bml should probably be renamed.

Maintainer/Moderator
Different things, but the words are often used interchangeably.

I think this terminology will also depend on whether we add an additonal control layer to communities, which was being talked about some time ago. John 22:47, 11 January 2009 (UTC)

Based on popular usage ("mods" as leaders of community), we may want to swap the two around: Mods are community owners, Maintainers (or some other name) are people who have limited maintenance control. (It'll confuse the heck out of LJ Support and Userdoc people, but in-the-wild usage might be saner.) --Isabeau 00:05, 12 January 2009 (UTC)


 * Except when you look at the actual meaning of "moderator" (somebody who moderates the content), it's a bit more limited in scope than what we mean when we say mod, especially since there is a moderation queue. I think there should be community administrators (admins), and then maintainers and moderators would be people who aren't admins but have limited control over things.  Admins have complete control over the community, ie ownership, and then they can dole out moderator/maintainer duties as they like (tags, moderation queue, comment freezing, banning, style editing, etc). This has the added advantage of NOT having to trust the people you give these duties to to boot you out of your adminship and take over the community. --Foxfirefey 00:26, 12 January 2009 (UTC)

Aren't we going to have fine-grained means of doing this later on after launch? It may be necessary to name with this in mind. I'd suggest "community admin" for now for what is currently a 'maintainer', though I don't have any ideas for 'moderator'. --Sophie 00:58, 12 January 2009 (UTC)