This is an official LiveJournal community where volunteers and staff members work together to coordinate technical support for LJ users. This journal is partially public, but is intended only for volunteers who are doing Technical Support. Anyone who needs help using LiveJournal should ask their questions in the Support center, not here.

Additionally, membership is restricted to staff members and volunteers who are holding the "supporthelp" privilege; all other membership requests will be rejected. However, you don't have to have membership here in order to participate in Technical Support -- just a few screened or approved answers each week counts you as an active volunteer for our purposes.

We ask that your comments to the entries remain respectful and on-topic. We reserve the right to screen or delete comments, or to ban users who repeatedly show disregard for this community's members.

That said, I hope you enjoy volunteering while you're here, and if you need links to further information on how to get started, please see our profile page.

Cheers,
Carrie S. (coffeechica)
Technical Support Manager

Hello! I'm speaking to you back there, trying to hide! Yep, you, the persons that have been thinking about helping out in Support and the ones that did actually answer a few requests.

So do you want to help out fellow LiveJournal users? It's easy to do so and we want to help you get started! The basics are explained here. Once you have had a look in there, just go ahead and try answering some requests.

If you want to improve in Support, there are a few ways to ask for help. First one is reviews, explained here. If you don't want to post there for whichever reason, you can always reach us by sending
an email at support@livejournal.com or joining us in IRC (info here).

We are a bunch of different people that enjoy helping others and we certainly love new additions to the team. So don't hesitate! Get started and ask for help any time you need it. We're looking forward to meeting you!

It's spring cleaning again, so I've gone through and tidied up the membership here so that the only members are either staff members, volunteers holding the "supporthelp" priv, or Abuse Team (/other auxiliary team) members.

As with any inactivity "deprivving", if you've been taken off the list and would like to come back, drop us a line at support@ and we'll see what we can do to help get you back in action again.

Hi, folks

Just wanted to let you know of something I just noticed on my Gmail account that may result in the occasional request. Gmail has always hidden duplicate content behind a link, but since they changed their web interface, this link is now represented by a rather inconspicuous icon. Some of the content hidden by this link includes the links that LiveJournal inserts at the end of every comment notification email.

( So, if you see any requests... )

* lj_pics_beta's Russian post had some inaccuracies yesterday. The post is updated. An English post will be coming to lj_releases after the weekend.

* The problem with people seeing the new SB interface when not opted into it has been resolved.

* The problem with people not getting CSS, etc is a CDN issue. The Moscow office is still working on resolving that (as they're in-office today, bless their (May-holiday) hearts). ;)

* More problems from this morning that I missed? Please (support-team) comment with them so we can make sure they're on the radar.

Just a quick note that elyssa has stepped down from adminning. She'll remain your friendly neighborhood lj_abuse correspondent, but is leaving Support.

Thank you for everything, elyssa! You did so much to champion the fixing of ScrapBook and help investigate problems with it, and helped so many people with your diligence. Don't be a stranger now. ;)

If the question is regarding broken notifications: give them 115 and keep it in General.

If they've done 115 and/or if they're missing from inbox too: that's Troubleshooting and somebody needs to ask ops about the Schwartz queue, especially if the inbox ones aren't generated.

No bugs at all should be in gunk. We stretch this rule for times of board panic, but their final resting place should be in Troubleshooting if it doesn't fit anywhere else.


As far as "are they actually fixed?" the answer to that question changes by the minute, which is why they should be in Troubleshooting, cause over there we have more of a direct line to eng/ops.

1) Yes, inactive accounts will be purged. We're following the rules from this news entry under "Purging inactive accounts". Yes, communities and identity accounts are included. Yes, the email has typoes in it but it's correct and trustworthy, except for the date it gives for purging (which is some time in the past). Yes, there will be a new news entry before the big red button gets pushed.

2) Due to a bug, the HTML cleaner is cleaning external stylesheets to the point where some don't work anymore. That's filed at LJSV-2055.

3) HTML cleaning CSS more strictly within the entry (similar to how it's stripped in comments) is actually not a bug, that's changed now too for security reasons, unfortunately.

4) Comments don't get exported to Twitter or Facebook anymore. Only entries are eligible for auto-posting now.

5) Speaking of Twitter, the Russian subjects thing will be fixed in r89. The problem with it not posting at all will be further investigated after that, though we suspect it may be a Twitter API issue.

I think that's all the new information I have to pass along.

aveleh and I haven't been able to connect to Jabber since the ddos started. Yet most others are able to connect without trouble. In case it's client related, I'd like to gather a list of who's affected and what they're using.

* I can't connect via iChat for OS X. I can connect via Trillian for OS X.
* Harold can't connect via Trillian for Windows.

[...please comment! It's ok if you're not a volunteer and you want to share your findings here. Reindeer Brig wants to know.] :)

Welcome to the many many new followers to this community! lj_support is a community that serves as a bulletin board for LiveJournal's support volunteers. This is not a community for end-user support. This community isn't a replacement for anything like news, lj_maintenance, or lj_releases. We're a lot more informal, and post quick status updates here from time to time just to make sure that volunteers have the info they need in order to help other LJ users. Our support model is based on users-helping-users, and has been so since Brad coded up a page for it in 2001.

If helping other LJ users get the most out of their LJ experience sounds like something you'd enjoy, you're welcome to plunge in and start answering unanswered questions! (That's the link to all non-Russian public requests. If you speak Russian, you're welcome to answer Russian questions as well.) Need more information on how this all works? Check out the Support guide. Need help? learn_support has a team of experienced volunteers who will be happy to assist you. We are quite short-handed at the moment and in a bit of transition in terms of volunteer leadership, but we'll do our best to make sure you get the help you need as a new volunteer.

There is currently a CSRF designed to mislead you into believing LiveJournal is requesting your username and password, when the data is actually being requested by a third party who is trying to gain access to your account.

The attack will appear as though someone has left you a comment, but an image similar to the following will appear requesting your password:




The domain used, liv i ejournal.com, is not livejournal.com, and you should not enter your password into any popup like this which appears.  The domain used by the attacker could change at any time.

If you have entered your username and password into any popup like this, you should immediately change your password at https://www.livejournal.com/changepassword.bml.

If any content has been deleted from your journal by someone other than you, please submit an abuse request.