( Why the change is necessary )
So fu has completely overhauled the process of replying by email. After our next code push, the reply form will be removed from notification emails entirely. Instead, you'll be able to reply to a notification email inside your mail client, just like you'd reply to any other email, and your reply will be posted to the site.
You can read the FAQ -- How do I reply to comments from email notifications? -- before the feature goes live, but ( some questions I anticipate )
Again, this will not be live until the next code push, but if you've got any other questions in advance, let me know! I think that as soon as you see it, you'll fall in love with it as much as I have -- especially if you're trying to juggle multiple accounts. :)
We will be doing a codepush in a few days, at about 9PM Pacific on Monday, April 22nd, 2013. Also known as 0400 UTC the 23rd, and a far different time if you're somewhere near fu. :-)
As always, we'll post to our Twitter account and this journal before the push and after to let you know what's going on.
We'll be doing a code push tomorrow about 9PM PST on Friday, March 1st, 2013. This is 0500 UTC on Saturday, March 2nd, 2013.
I don't expect any troubles with this push. As always, please watch our Twitter account and this community for updates! Thanks!
I just rolled out some search changes. The two main things you should notice: search indexing is much quicker now (it updates with new content every 15 minutes) and also now comments (on paid accounts) are indexed.
Thank you for all of your patience with search. We outgrew our old trusty search machine and it's now retired. The new one is much larger, has faster disks, and should hold us in good standing for a while as we grow.
I'll be around all day and watching this post. Please let me know if you see any problems!
Connectivity appears to have been restored at this point. We're really sorry for the inconvenience.
We'll keep you updated if it looks like we're going to run long, but we're hoping to complete this in 2 hours or less. Watch the offsite status Twitter account for updates.
EDIT: And, we're back! Just goes to show, when mark estimates an hour and you schedule 2 hours just to be safe, everything will finish much faster than that.
We've noticed a few instances of icons not loading, and are looking into it.
The maintenance window will begin tonight at midnight EST/9PM PST/5AM UTC. (See this in your timezone.) We're tentatively allocating 2 hours for the work; it may be longer or shorter depending on what we find when we dig into it.
We're going to try doing this with the site in "read-only" mode, where you can read existing entries and comments but not make new ones, rather than maintenance mode, where the entire site is unavailable with a "down for maintenance" splash page replacing all pages. It may prove impossible, though, so if the site switches from read-only mode to down-for-maintenance mode, don't be surprised.
Watch our offsite status for updates -- we'll keep you posted there as things develop.
The site outage is over. My apologies for the downtime.
One of our databases filled up its disk and went offline, and this caused the site to stop responding. We failed over to the backup database and everything is now back up and running.
Everything should be working. Please let us know if you see any trouble.
We will need to schedule a maintenance window soon to handle the full database and rebuild the cluster so we have a pair again. Stay tuned to this account to watch for announcements about that.
( More technical detail... )
A note: any users who have enabled journal-styled icon pages will have that feature turned off as a result of one of the bug fixes. You can turn it back on right away, though! It's under Journal Icons Style on the Display tab in Settings.
EDIT: All done! Report any bugs/errors/problems/squids in comments, please. Thanks!
(To complicate things, sometimes the crosspost attempt will actually succeed, but LJ will report a failure anyway. You should double-check to see if the post actually did crosspost anyway if you get an error.)
Posts will attempt to crosspost several times before failing permanently. Once you get the notification of the permanent failure, you can try to crosspost again by editing the entry and checking the crosspost checkbox.
Also, a very happy new year (Gregorian) from us all to you!
Due to some recent availability problems with accessing the LiveJournal service, crossposts may be slow. The system does automatically retry, but if it's a slow spot it could be minutes or even an hour or two before we can get the entry posted.
Thank you for your patience!
So, for at least the next few days, you might notice that the option for commenting as an OpenID account doesn't appear sometimes when you load a comment form, or if you're logged into an OpenID account you might randomly get weird errors or seem to be logged out, etc. If that happens, just refresh the page until the problem clears up. (When you ask for a page, you get sent to the webserver that's next up, so about 1/4th of the time you'll get one of the webservers with the problem.)
We'll have this fixed as soon as possible! Sorry about the trouble.
(EDIT: And, back up it goooooooes! Bouncey bouncey bouncey. alierak has been exerting herculean efforts to squeeze every last bit out of the current setup, so search may or may not be available at any given moment. It's Schrödinger's search! So, if you want to search for something, give it a try, but don't be surprised if it's slow, out of date, or down entirely at any given moment.)
Edit: This is done, the code has been pushed!
In the next few minutes, we'll be doing a code push on Dreamwidth. You can expect a bit of a rocky experience tonight, since we will be not only deploying new code, but also doubling our caches -- which means that the site will slow down for a while, then will get faster than it was!
If you see any problems, please comment here and let us know. We have all hands on deck to make sure everything goes smoothly.
2) In addition to the code push we have scheduled this weekend (see previous announcement for details and times), we will be adding two new webservers sometime in the next week or so. (And by 'we', I definitely mean mark this time.) Until our provider can build them and Mark can configure them properly and add them into the webserver pool, the site may be a bit sluggish at peak times, usually early evening.
I like this thing we have going on here where all of our problems this week are a result of people using the site to make and do awesome stuff. CARRY ON, FOLKS.
We've got a plan that involves a new search database server (to go along with the two new webservers we ordered today), a new database schema that will make indexing, storing, and accessing search data much faster, and a method of storing and retrieving search data that makes more sense for the way usage has developed now that we have more information on what actual usage looks like. (And by 'we', I once again mean 'Mark'. There is a theme here.)
The plan is going to take a week or two to implement, though, and until then, search results will continue to be out of date. Anything that is already in the search database (as of about 10 days ago) will still be searchable, but newly-made posts and newly-imported posts won't show up until after we can fix it.
We'll let you know when the problem is fixed. Until then, continue on being awesome and making stuff: we'll catch up to you as soon as possible.