Title
Commenting

Short, concise description of the idea
Would like to be able to comment on 'my friends' page directly, without opening each post separately.

Full description of the idea
It is very frustrating to open each post separately even when I want to write just one word. I have to open them in new tabs and by the time I got to the bottom of 'friends' page I have about 5-10 tabs open.

If it is possible to make it similar to commenting on Facebook it would make life much easier. E.g. when I read posts I can comment straight away, without opening the post.

I got this thought when I asked my friend why is she commenting me on Facebook and not commenting on LJ. She replied that on LJ it takes too long to open the post and that on Facebook she can do it much faster.

• More people will be commenting
• more socializing
  

• It might be difficult to change the engine code to add such option

Title
Allow community maintainers to subscribe to other communities' ban lists.

Short, concise description of the idea
Give the community maintainers the ability to share their ban lists with other communities' moderators.

Full description of the idea
Livejournal suffers from hordes of bots that post scam into multiple communities. The text and links may vary, so it's inefficient to filter the posts automatically. However, a human moderator can always tell a bot from another human and ban the former.

I suggest to add a feature that allows a maintainer of one community to subscribe to other communities' ban lists. That is, if someone bans a bot from his community A then it will automatically be banned from other communities subscribed to A's ban list.

Note that this is not the same as the "Report a bot" feature. At the present time if a bot bombs several communities a ton of users reports this fact, but the scam postings won't disappear until the malicious account is considered a bot and blocked. On the other hand, if one of these users is a community moderator that bans the bot, the postings should automatically disapper from all the communities that are subscribed to his banlist.

• The amount of spam will reduce drastically, as people usually trust the maintainers of large communities and will adopt their banlists.
  

• Such an approach may cause propagation of human user bans across several communities. This is hard to avoid, but shouldn't be a common problem.

Title
Journal or profile link in plain text defriending notice

Short, concise description of the idea
The plain text defriending notice should have a link to the journal of the person who just defriended you.

Full description of the idea
When I get a defriending notice, my first impulse is to go check out their journal. Sometimes this is to see if they have left an entry that says why they have defriended me, or whether they have defriended other people that I know they previously had friended, or just to remind myself who they were, in case they added me and then we never interacted and I don't recognize the name. I can't be the only one who does this.

The defriending notice has a list of links and suggested actions, which does not include "view their journal" with a link; the text email does not even include a link to their name when saying who has defriended you.

The defriending notice email should either have a "view their journal" link for both plain text and HTML, or have a link to their journal when it says who has just done the defriending. Their journal is linked in the HTML version.

Instead of "exampleusername has removed you from their friends list", have "exampleusername (http://exampleusername.livejournal.com) has removed you from their friends list".

• Easier for a common use case upon being defriended.
• Leaving out the link doesn't stop people who are determined to cause a ruckus from doing so, and it doesn't even make it significantly harder.

• Adding "You can view their journal" to the list of suggested actions would probably be a bad plan as it would tacitly endorse trolling and other forms of drama. (If this is implemented, it should be a link next to their name when it is first mentioned.)

Title
"Quick Update" text box at the top of the LJ and Friends List pages

Short, concise description of the idea
In order to facilitate more frequent, status-style updates, I propose adding a one-click text entry box right at the top of the page, both on the main livejournal page and in the header bar of the Friends Page view.

Full description of the idea
Livejournal is being killed by Facebook. People like the quick, no-committment nature of a "status update" box. It also entices people to post content when a small text box is right at the top of the page they most frequently visit (in LJ's case, I believe this is the Friends Page view).

Just trying to bring some life back to LJ. Let's make it easier for people to post little snippets and updates.

• Brings traffic back from Facebook and Twitter.
• Makes it easier to participate in the LJ community.
• Expands the unspoken commitment of Livejournal from "OMG you need to post a big long blog entry" into "or you can send out a quick update," psychologically speaking.
  

• "Quick Update" entries would be sent with no title.
• Fitting a text box into the current Friends page header may be a tight squeeze.
• LJ may wish to define itself more as a long-content blog forum, rather than a snappy social networking site like Facebook or Twitter.

Statistics are here!

You can now see the number of people who have visited your journal, your individual entries, a chart of comments, readers of the RSS feed of your journal, and the last 100 logged-in users who have visited your journal directly (if you've enabled My Guests).

Things you should know:
-Stats are completely anonymous (only My Guests is tied to username); only numbers are recorded, not any other information
-The times and dates in the graph are based on server time, which is UTC/GMT
-The light grey number at the top left corner of the graph is the statistical outlier
-While the graph may go back in time to this summer, the stats-gathering server was not on constantly, so previous stats may be missing. Today, and going forward, full stats are collected and displayed.
-If you opt out of My Guests (meaning that your username will not show up on other people's reports and you will not be able to view your My Guests tab), it does not affect your use of the rest of the Stats - if you're a Paid or Permanent user, you'll still be able to see all the rest of the information on this feature

( Page-by-page walkthrough )

If you have a Paid or Permanent account, you can now send 10 of your non-Paid friends a $10 coupon. Your friend will be able to purchase a Paid Account for $9.95 (instead of $19.95) for one year by enrolling in our automatic payment plan or make a manual payment of $15 (instead of $25).

• All Paid and Permanent accounts can send out the coupons by clicking here (it's also under Friends -> Holiday promotion in the site header)
• You can also send to people not on your Friends list by manually entering the username in the field provided
• If your friend declines the invitation, it will be returned to your available invitation pool and you'll be able to send to someone else
• You can send the invitations until January 15th

There's quite a lot in this one - here are the details:

**Gift a $10 coupon
All Paid users will be able to invite 10 friends to purchase a Paid Account with a $10 discount. This can be found in the header under Friends -> Holiday promotion

**Journal Statistics
Journal Statistics and My Guests have arrived! They can be found in the header under Journal -> My Stats: Full Statistics are reserved for Paid users and My Guests are for everyone!

**New community moderation setting
Maintainers of communities which allow unmoderated posting can now choose to moderate only entries containing links to non-whitelisted domains. The new setting (if you're the maintainer of a community) can be found at Manage Communities -> Settings -> Community Moderation. The whitelist for the community is pre-populated with "trusted" sites, and the maintainer can add and manage the list as well.

**Free Sponsored v-gifts
For one week (December 16-23rd), a selection of free v-gifts will be available. Since they're from a Sponsor (3M TMI App), only Basic and Plus users will see it in the v-gift store. Paid and Permanent users can find it by clicking here.

Bugfixes and other changes:

• New holiday header!
• The new text search is now the default link in the header
• Scrapbook status should now correctly follow journal status when a journal is deleted, purged, or suspended (LJSV-693)
• When switching from the HTML editor to the Rich Text editor the cursor now stays where it was (LJSV-487)
• Firefox spellcheck (and all browser-native context menus) now work in the RTE (LJSV-571)
• The RTE no longer inserts extra list items when an lj-cut is placed (LJSV-583)
• The pop-up item "Type your cut contents here" once again appears when the lj-cut function is used before highlight text to go under the cut (LJSV-792)
• Added language-stripping to the HTML Post an Entry form (LJSV-301)
• Long entries now display properly in A Novel Conundrum style (LJSV-623)
• Indentations and spaces now work as expected in the RTE (LJSV-797)
• Problems between Safari and the RTE have been fixed (LJSV-648)
• Added support for internal tagging of Support Requests (LJSV-790)
• The Rich Text Editor has been language-stripped for translation (LJSV-830)
• The initial setup for TxtLJ now happens on the TxtLJ setup page (subsequent changes can then be made on the Mobile settings page)
• Implemented referer check in the mogupic script - thank you, DW! (LJSV-500/DW-888)

Known Issue: Maintainers of unmoderated communities may see the radio button for the new community moderation setting checked. However, it is not on by default; this is a bug. The moderation settings will remain unchanged until the Maintainer clicks "Save changes".

Title
Change wording on /contact to clarify the feedback vs. suggestions process

Short, concise description of the idea
"Feedback" can be suggestions intended for staff's eyes only too. "Suggestions" is for public discussion in suggestions Clarify that.

Full description of the idea
I'd like a change to the /contact page clarifying the feedback vs. suggestions process in the LiveJournal contact form.

In addition to someone's opinions on policy and so forth, one can technically make suggestions in private to staff through the feedback form.

Things submitted to the suggestions form are deposited into the moderation queue for the LJ suggestions community.

Clarifying that "feedback" is for feedback to staff and suggestions that are not intended for public discussion, and "suggestions" are for suggestions intended for public discussion, would probably improve user experience; a number of people who submit suggestions are not aware that their suggestion may be presented for public discussion, and some would prefer to make the suggestion in private.

• People might share more ideas and be less intimidated by the thought of plunging into the free-for-all discussion in suggestions, if they know there is that option.
• People who want to contact staff privately will see that the suggestions form is not the place to put that information.
• Less confusion when people are surprised that their suggestion goes to suggestions.

• More workload for employees working on the Feedback board.
• Users may expect personal responses.
• The public discussion part of the suggestions process sometimes produces great things, and staff may not have time to subject privately-submitted suggestions to the same rigorous debate/brainstorming process.

Title
Re-subscribe to a deleted/changed-away tag if a new tag of the same name is made

Short, concise description of the idea
If you are subscribed to a tag and that tag is deleted, then later a new tag of that same name is created, the subscription should pick back up unless you have made changes.

Full description of the idea
Currently, if you have subscribed to a tag in someone's journal, and they delete the tag or change the name of the tag, you are left with a broken subscription. If the user creates a new tag or renames a tag back to the same name you were subscribed to, your old subscription ought to be automatically re-activated it, provided you had not deleted it in the interim.

• Would allow people to do tags management freely without worrying about messing things up for their subscribers.
• More intuitive.

• Would interfere with the ability for users to clear out "stalking" subscribers by deleting/renaming and then re-creating their tags.

Title
Tag subscriptions should follow tag name change

Short, concise description of the idea
When you are subscribed to a tag, and the journal owner changes the tag name, you should be subscribed to the new tag.

Full description of the idea
When you're subscribed to new entries with a certain tag in a certain journal, if the owner changes the name of that tag, you should be automatically subscribed to the new name of the tag.

(Currently, what happens is buggy, and gives you a broken subscription instead of a sensible error message; a support request to fix that bad behavior has already been filed, but since it doesn't give you a subscription to the new name, that would be a new feature.)

• Intuitive behavior.

• If the user makes everything in the tag not viewable by you and changes the tag name, this could break security.
• If the new tag has nothing to do with the old tag, this could be confusing.

Title
Editing entries

Short, concise description of the idea
To be able to select a range of dates when editing entries

Full description of the idea
To be able to select, say, "all entries between 1/1/2008 and 6/1/2008", rather like Quicken allows you to select a date range of entries to see. I have no coding skills, so I cannot begin to say how to do it.

• When having to change the security on old entries (friends locking certain ones), you wouldn't have to use the "Last 26534 entries" to see which ones need to be altered, or go back page by page through all old entries and then select it by date.

• I can't think of any drawbacks, but I'm sure there are some.

Title
Viewing Posts

Short, concise description of the idea
You desperatley need to make it clear and easy to view recent posts.

Full description of the idea
Please make it clear where the link is on the home page to view recent posts. It took me forever to figure out that i need to click my name to get to the page. That is confusing. since writing entries is the basis of this page, it should be much clearer and easier to get to the page where you can view all of your posts. People like reading what they have written so this should be an easy option. not something we have to look for.

• the biggest benefit is the lack of frustration trying to find your own damn posts.
  

• you will have to find some space to add one link. Shuoldnt be that bad.

Title
Community Management: Option to ban member when removing an entry

Short, concise description of the idea
When deleting an entry from a community (being the community maintainer), you have the option of banning the poster as well when removing the entry.

Full description of the idea
Maybe it could be a radio buttion option set to no by default (Ban user - Yes - No) or a check box. But the option to ban the user and the entry could be on the same page.

• It would save the trouble of going to the command console and banning members manually, one at a time.

• I'm not familiar with the way it's structured the way it is, so maybe there is a drawback and a reason you have to go to the console?