
Hope you have fun!

A bug where </ in a community's displayed name was not properly escaped, breaking the link to leave the community, was fixed. 
Show the moderators and preapprove columns if the community is moderated or there are members with moderation or nonmoderated edges. 
Quick Reply was added to old style comment pages (S1, and S2 styles which use the old style comment pages. 
When the Meme tracker is disabled, it will not appear on the sitemap. When it is enabled, it will.
The S2 colour picker now links to the correct images. 
More preperation for fotobilder. 
Friends groups and memories are now clustered and memcached. 
Outgoing mail submission between the webservers and the mail servers has been sped up. 
Problems with poll labels and having more than one poll per page (friends) was fixed. 
Disable password retrieval for new communities, because communities no longer have passwords. You should do everything to manage your community while logged in as the maintainer account, by using the "Work as" option at the top of the page. 
The bad password error on the Create a Journal page was edited to be more clear that passwords cannot be based on a dictionary word and why. It now includes the FAQ as well. 
Infohistory now records when a password is reset as a result of changing community --> personal. 

When you add a memory to your entries, there is now a link to take you back to the entry you were viewing. 
When you add new members to your community, the default action is to give them posting access. This was the case before, but not in an explicit way, so that if you didn't want to give them posting access, they still got it. 
When editing multiple entry via editjournal.bml, the icons that display whether the entry is friends only or private are now displayed. 
The charset is now included in the headers of http: will displays as Link to exampleusername's userinfo.
When you make changes to the members of your community, LiveJournal now tells you which changes you made. 
A bug was fixed for users of Norton Internet Security. Norton replaces header fields with tildes, and LJ choken on that. 
An issue where users were having trouble editing their most recent entry was fixed.
S2 now returns human redable errors instead of dying. 
When a user clicks a link on the secure site (for example after changing their password or buying something from the store) that would give a 404 error, they're redirected to the regular site. 
Fotobilder + post by e-mail + new lj tags. Fotobilder isn't live yet for users, so this is still preperation stuff. 
Quick reply now works with robots being blocked. 
A bug where users cannot view the memories of other users has been fixed. 

The Edit Pictures page now stops downloading a picture when it reaches the max of 40KB, so when a user tries to upload one that is over that limit, the page doesn't have to download the entire (potentially huge) picture first before erroring.

When a syndicated account is created, the feed URL is now checked to make sure it's a valid RSS/Atom/RDF file before downloading the entire thing.

Syndicated accounts can now use feeds that use ports other than the (standard) port 80.

Invalidly encoded subjects now won't cause problems when being displayed on the Support Board or in the requests themselves.

A bug with the new "Screened Comments" option in the web interface update form (update.bml) was fixed. If you selected "None", then the entries would give the message saying that anonymous comments were being screened, even though they really weren't. The actual behavior works fine (no comments are screened when "None" is selected).

Space for PicPix quota information was added to tekihatu.org/megateenbbs.com/bbs/manage/files.bml, in preparation for integrating PicPix hosting on LiveJournal.

There was a bug with the new "e-mail me comments that I post" feature, which displayed the wrong journal name in the e-mail. This was fixed.

A new transform was added to the S1 style system to allow people to create URLs to journals and communities appropriately (/users/username vs. /community/commname). You'd use %%userurl:username%% to display the users form of the URL and %%userurl:commname%% to display the community form of the URL.

When setting PhonePost transcription options, the "No one but me" option was not saving. This was fixed.

The bug was fixed where if you typed in a syndicated account in lostinfo.bml, it'd say that an e-mail was sent with the password. However, syndicated accounts do not have e-mail addresses or passwords, so the message was changed to give an appropriate error if you type in a syndicated account.

The bug with the Feedster journal search feature was fixed, so now it should work properly and only display results in the journal you were searching.So our load balancer retrieves all incoming web requests immediately after your browser sends them, then sorts those requests into two lines: free users and paid users.

Whenever a real server (not the load balancer) is ready to do more work, it always fulfills a request from the paid user line, and only does free user requests once no paid users are waiting.

We've had this done for a couple weeks, but just put it live today. We were going to wait to announce it until we had the cool part done, but thought it best you all know what's up. The cool part is: we're going to make the load balancer tell the real servers how many seconds/milliseconds you saved by cutting in line and how many people you cut in front of, and then the real servers will add that to the response, so you can do "View Source" in your browser and at the top it'll show you those stats, so you can verify it's working.

This is all different from what we did a few years ago, which was to have "free servers" and "paid servers". Instead all the servers do both free and paid, but access to the servers is prioritized by your account type.

Here are some stats of it in action:

queues
web_proxy-normal.age 0
web_proxy-normal.count 3
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.
queues
web_proxy-normal.age 0
web_proxy-normal.count 0
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.
queues
web_proxy-normal.age 0
web_proxy-normal.count 4
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.
queues
web_proxy-normal.age 1
web_proxy-normal.count 4
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.
queues
web_proxy-normal.age 0
web_proxy-normal.count 3
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.
queues
web_proxy-normal.age 0
web_proxy-normal.count 5
web_proxy-highpri.age 0
web_proxy-highpri.count 0
.


At the top it showed there were 3 free users (waiting for less than a second --- age 0) waiting to get responses, and 0 paid users. Then it was all clear, then 4 new free users were waiting, then waiting up to a second, then those cleared, and 3 new free users were waiting under a second. Then 5 later, still under a second.

But throughout, no paid users were ever waiting.

Obviously the above isn't an interesting demo of this feature, but next time we hit a hiccup and the site gets slow, the paid users will be affected the least, since you won't have to wait in line long for a page to be generated. (just have to wait for paid users that came before you)



