fiddlingfrog has been added as docadmin.

Congratulations! They're all yours, chap! (New docadmin clears out, etc.)

FAQ32
It appears that the place where you can enter your last.fm username is no longer on the Edit Profile page. This means a section of FAQ32 needs to be edited to include the new location: http://www.livejournal.com/manage/settings/?cat=extensions.

FAQ 338 has some info on the "suspicious comments" thing, but I think it needs expansion.

1) People don't realize that once/if a comment has been sorted into the suspicioius comments section, deleting it will automatically mark it as spam. (It would be preferable for the "comment deleted" message to say so, but this is easier I think).

2) Journal owner is the only person to see the suspicious comments.

3) I'm not sure if this is from the comm's manual whitelist, general community whitelist, the spam protection, or an unholy combination of the above, but sometimes comments are screened. The FAQ should make it clear that it's from one of those and then links to how to get rid of it/instructions on how to disable the autoscreening, since many sites get blacklisted.

(ah, also, can someone add the tag "faq338"? I can't create tags.)

FAQ250 has a section named Further Reading. The only thing in that section, the link "FAQ category: Customization in the Old Style System" goes to a place that does not exist.

Sophie mentioned on IRC that there is a section of FAQ 72 that explicitly states a preview button is available for comments. This hasn't been true since R88.

Similarly, FAQ 15 says only Paid users can edit comments, which was changed shortly after R88 as a result of the preview function going away on the new site scheme pages.

Addendum, 4/11/2012:

FAQ 131 also lists the ability to edit comments as a paid account feature.

Would it be useful to have a table in 225, 330, or 332 (or maybe all of them) showing the differences between what an owner, maintainer, and moderator can do? Something like this, with appropriate cross-linking as necessary:

Version 3

	Owner	Maintainer	Moderator
Community settings
Rename community	x
Delete community	x
Remove maintainers	x
Add new maintainers	x	x
View and change community settings	x	x
Change community style	x	x
Membership
Invite, remove, or ban users. Appoint or remove moderators	x	x
Approve or reject requests for membership (if applicable)	x	x	x
Entries
Delete entries	x	x
Approve or reject entries in the moderation queue of a moderated community	x	x	x
Create tags	x	x	#
Add tags to entry	x	x	x
Remove tags from entry	x	x	#
Comments
Delete comments	x	x
Freeze comments	x	x	x
Screen comments	x	x	x
See screened comments	x	x	*
Unscreen comments	x	x	*

^* - When a moderator screens a comment, that comment is collapsed but a link remains for the moderator to unscreen the comment. If they refresh the page, that comment will then be entirely hidden and can't be unscreened.
^# - While a moderator can always add existing tags, they can only create new tags or remove tags from an entry if the "Who create new tags and add/remove tags from entries" on Manage Tags is set to Members Only or Any User

I updated the "warning bar" at the top of FAQ 248 to reflect the fact that, although the FAQ is in the "Advanced Customizations" category, only some of the customizations discussed require a Paid account. For example, adding a header image or anything else that just requires fiddling with options on the Customize Journal Style page doesn't. Also, some layouts (not restricted to Paid accounts) can reverse the order of entries on a page, so it wouldn't be correct to say that a Paid account is required to be able to reverse entry order.

FAQ68
I think in the sentence "Most methods of embedding your website require that you know your style's identification number" - your website should be your journal.

Do you agree?

...to reflect that we no longer support IE 7.

LiveJournal does not support feeds URLs beginning with anything other than "http://". This excludes not only the "feed://" pseudo-scheme but also SSL sites whose URLs start with "https://".

I can imagine that supporting SSL is technically not a problem (I presume that LWP::Simple, or whatever LiveJournal uses to fetch feeds, supports SSL), so this might be either a policy reason (to reduce load?) or an oversight (in which case I presume that suggestions might be the place to turn).

In any event, while the restriction applies, it would be good to document this; the error message, "The URL you have typed is invalid. Please make sure you have typed the URL correctly and try again.", is not terribly informative since https:// URLs look fine to most Internet users.

So I would suggest at least adding this case to FAQ 151 "Why might a syndicated account not update correctly?" (unless you can think of a better place; say, FAQ 137 "How do I watch feeds on my Friends list? What are syndicated accounts?" which explains how to create one?).

Something along these lines, perhaps?

Invalid or unsupport URL scheme: LiveJournal only supports feeds whose URL starts with "http://". If the feed URL you have starts with "feed://", replace it with "http://"; if it starts with "https://" or anything else other than "http://", check to see whether the content is also available from a plain "http://" URL.

FAQ 290 thinks the latest version of the iOs app is .6 and does not mention that there are apps for Android, Windows Mobile, or Bada, all of which are linked here: http://www.livejournal.com/devices/.

It hasn't been updated since 2009.

[Edit] And we have a second draft:

Subject: What are cookies? How do I delete LiveJournal cookies from my browser?

Cookies are small files stored by your browser which are used to identify you to the website you are visiting. Generally, this is to provide you with faster, easier access to the website.

How to delete cookies stored by LiveJournal varies depending on which browser you are using. Below are instructions on how to delete cookies in the most recent version of the browsers LiveJournal supports:

Firefox (Windows):

1. In the "Tools" menu, select "Options".
2. Click on the "Privacy" tab, then click the "remove individual cookies" link.
3. In the search box, type livejournal, select all cookies found, and click the "Remove Cookie" button.

Firefox (Mac):

1. In the "Firefox" menu, select "Preferences...".
2. Click on the "Privacy" tab, then click the "remove individual cookies" link.
3. In the search box, type livejournal, select all cookies found, and click the "Remove Cookie" button.

Chrome:

1. In the Chrome/wrench menu, select "Options" (Windows) or "Preferences..." (Mac & Linux)
2. Click on "Under the Hood", then click on "Content Settings".
3. In the "Cookies" section, click the "All cookies and site data..." button.
4. In the search box, type livejournal, and click the "Remove All" button.

Internet Explorer:

1. Open Internet Explorer and go to http://www.livejournal.com/.
2. Press F12 on your keyboard. A box should open up at the bottom of the screen.
3. In this toolbar, open the "Cache" dropdown, and select "Clear cookies for domain".
4. Select "Yes".

Safari:

1. In the "Safari" menu, open "Preferences..."
2. Click the "Security tab", then click the "Show Cookies" button.
3. In the search box, type livejournal, select each cookie found, and click the "Remove Cookie" button.

Opera (Windows):

1. In the Opera menu, select Settings, then Preferences.
2. Click the "Advanced" tab, select "Cookies", then click the "Manage Cookies" button.
3. In the search box, type livejournal, select each cookie found, and click the "Delete" button.

Opera (Mac):

1. In the "Tools" menu, click "Private Data..." A dialog box will appear.
2. Click the small triangle to the right of the words "Detailed Options".
3. Click the "Manage Cookies" button.
4. In the search box, type livejournal, and select each cookie found and click the "Delete" button.

Note: How to delete cookies may vary slightly depending on the version of your operating system and browser.

FAQ307 suggests both Google Analytics and Google Webmaster Tools can only be used by Paid and Permanent accounts. This appears not to be true for Webmaster Tools. Myself and others have tested this with a Plus account. The "upgrade" thingie only shows up next to Google Analytics, and the Webmaster Tools text box is not greyed out.

To start off, I never used the navstrip before the major update a few months ago. When I did enable it I was really pleased to find out that the calendar function on the navstrip lets me (and presumably anyone with a paid/permanent account) use the date function of the friends page much easier than having to manually add ?date=YYYY-MM-DD to the URL.
Unfortunately, when I went to answer a request today and add that info to my answer, having seen the requester with the navstrip on their journal, I couldn't find it in any FAQ. I' mnot sure if it should go in 219 with the reading by date info, or in 264 with the navstrip info. In fact, it's been two years since 264 was updated at all, so maybe a listing of the features available on the strip would be in order.

With release 83 yesterday, the 'Spam protection' checkbox over here now covers both comments and private messages. So the following is the FAQ draft for this feature. This would be a FAQ that is linked to from anywhere that's talking about controlling comments, comment spam, unwanted comments, etc, such as:

-- FAQ 23 - How do I control who can post comments in my journal? - Put a bullet point of "Activate the Spam Protection feature" at the bottom of the bullet point list, then remove that hastily-added last paragraph.

-- FAQ 201 - How do I mark a comment as spam? What does this option do? - Stick a line in here somewhere about "If you are receiving spam comments, go activate blah blah."

-- FAQ 109 - What should I do if I'm receiving harassing or unwanted comments?" - Same sort of thing. "If you're receiving spam, blah blah."

There may be other locations as well, but those are the obvious ones I saw.

Also note that this is intentionally non-specific as to how things are actually identified as spam. We do not want to be broadcasting what we're considering to be spam or how our systems are making determinations, etc.

NOTE: The images are just quick crappy things I did in Paint just to show "here's what images likely work here." When this is taken and put up for real, I'm sure a designer can get us better quality images than these.

---

Title: "How do I help protect myself from receiving spam comments and messages?"

The Spam Protection setting can be activated to help automatically identify potential spam comments and messages. Activating the feature will take the following actions for both comments and private messages; it is not possible to activate it for only one or the other.

Spam protection for comments

When Spam Protection is activated, comments posted to your journal which our system has identified as potential spam based on a variety of criteria will be automatically marked as spam and moved to a suspicious comments section. Any comments posted by users you have added as a friend will never be automatically marked as spam.

When viewing an entry with comments that have been automatically identified as spam, you will see a '[#] suspicious comments' link next to the total number of comments that have been posted to the entry.



Click the 'Read suspicious comments' link to review the potential spam comments at any time. If an individual comment is not actually spam, you can use the Not Spam button to unscreen it and move it to the main comments page.

Spam protection for messages

When Spam Protection is activated, private messages from users who have been identified as potential spammers are marked as spam and moved to a special folder in the Inbox. As with comments, you can review these messages at any time to either delete them or mark them as not spam.

FAQ 160 could use instructions for clearing the cache for the following browsers:
Internet Explorer 9
Firefox 5 (both Mac OS and Windows)

Would people who have these browsers like to write up instructions and post them in a comment here? Thanks!

There's rather embarrassingly broken markup on FAQ 299.

I believe the mistake is in paragraph beginning "To sign up, log into LiveJournal and click".

We're adding this at the request of the Russian Support team. This is a draft that came from a draft that came from a Russian draft. Assault it, please. I'm looking especially for:

* quick reference (the wiki is the place to put How Support Works)

* consistency of nomenclature (or, "calling something by the same name all the time")

* wikifying (you know what I mean)

----

( beware of documentation lemurs )

The per-entry comment settings are Journal Default (whatever you set on the Account Settings page), Disabled (no comments allowed. If chosen later on entry edit and comments exist then those comments are hidden), Locked (only selectable when editing the entry. Prevents new comments and freezes all existing comments), and Don't Notify (Journal Default setting for who is allowed to comment, but you won't receive any notifications about comments made to the entry).

These options don't seem to be documented anywhere. FAQ 23 lists Comment Setting per Entry but doesn't explain what they are and FAQ 62, which is linked from the ? icon next to Allow Comments? on the Post an Entry page, doesn't really mention per-entry options at all.

FAQ 23 seems the logical place to include them, but FAQ 62 is where the help icon links to. Any thoughts?

Hello everyone. There's been a lot of confusion about the volunteer role in lj_userdoc. And that's mostly on us; we've been in a state of confusion about it ourselves. Today we had a meeting that should clear some things up for everyone.

One of the most frustrating parts of being a volunteer docadmin is having to write FAQs for features that just went live: features that you never knew about in advance, but suddenly you feel pressured to be such an expert on the feature that you can instruct others how to use it. That's something that's never been fair to you, and so for the last year or so, we staff members have been writing new FAQs ourselves whenever possible.

However, it is evident from looking at the frequent posts in this community that LJ users still want to be a part of this process. And I really want to keep this volunteer team open for many reasons: mostly that you're really really good at finding our mistakes and telling us. ;)

As Bethany is no longer on staff, editorial duties fall to Michael (mike), and I will be assisting him in the technical aspects of getting faqedit to work. We will be working on getting the new FAQs together and posted, which is going to be a massive process as many of the existing ones were split, merged, and spliced. (And we haven't even talked translation yet. Oy.) But the one thing that we know for certain is that we will need help with the details, which is exactly where the lj_userdoc community shines.

Since some of you have asked: Michael & I have no idea when the new stuff is going to be ready (actually, it's gonna be "lj soon"), so things marked "status-pending" can probably still be done for the sake of helping users now.

As always, being an LJ volunteer means doing something that you enjoy in order to help other users. Those of you with FAQ editing privs: if this sounds like something you want to remain a part of, let me know. Those of you without FAQ editing privs: we need people, so if this sounds like something you want to become a part of, let me know. If you want out, let me know that too. Comments are screened by default; I will unscreen only with your permission.

While FAQ #150 mentions that other account types cannot be converted into syndicated accounts, and that syndicated accounts cannot be deleted or edited it does not also mention that syndicated accounts cannot be converted into other account types.

FAQ #175: By default, comment pages display in the site scheme used for any LiveJournal page.

Paid, Permanent, and Plus accounts: Custom comment pages match your journal's theme by default. You can either modify those custom comment pages further, or switch to comment pages in your site scheme by setting the option "Disable customized comment pages" to Yes, in the Presentation section of the Customize Journal Style page.
Early Adopter and Basic accounts (or any account using the old style system): Comment pages always display in your site scheme.

Maybe it's just me, but I find this part difficult to grasp, esp. for new people. After reading it a few times I now believe it's because the info about the Early Adopter and Basic accounts only says "comment pages always display in your site scheme" which is basically what the first sentence said about the default for all accounts already. For Paid, Permanent and Plus accounts there is a detailed explanation about customization. For the other accounts there should be a note that this isn't possible for them. Especially for new users with Basic Accounts who don't quite understand the difference between style/journal theme and site scheme this may sound as if the comment pages should match their style as well. My suggestion would be to switch the parts of the different accounts and start with Early Adopter and Basic, saying that the comments for them appear in their site scheme (e. g. Horizon), not in their journal style.
Underneath, the customization features of the other accounts could be mentioned.

Again, it's probably just me and last time I read it I was tired. But even now it took some time until the difference really sank in, so this small change may help other people as well.

In FAQ 46, it says that Basic and Plus users can purchase 'purchase one or more userpic addon-ons'. I think that last word should instead be 'add-ons'.

FAQ 82 lists the URL for a community incorrectly; they should show as user URLs now. Thanks!

FAQ 23, "How do I control who can post comments in my journal so that I don't get any comments from that guy I hate so much?", has been updated with a base-level paragraph on the Spam Protection checkbox. It's the last paragraph of the FAQ.

This is just to get something in there at some level so it can be referred to in answers -- those with editing privs should feel free to clean it up or augment or pare down as necessary. :)