Home : News

News

Welcome to LiveJournal news. If you crave more frequent and detailed news, check out the following journals:

userinfonews Infrequent, basic, overall news. (this page) RSS Feed
userinfolj_maintenance Server status and planned downtime announcements. RSS Feed
userinfolj_dev LiveJournal technical development & planning. RSS Feed
userinfochangelog Every little change, as it happens. RSS Feed
userinfolj_test The testing community, for testing the above changes. RSS Feed
userinfolj_biz LiveJournal business-related community. RSS Feed


[ << Previous 5 ]

January Status Report

Thursday, Jan 29th, 2004 -- 11:01 am

jproulx
We now host over 2,000,000 users, roughly half of which are active in some way. It's only been 9 months since we hit 1,000,000, so it's nice to know so many people have chosen LiveJournal to host their journals!

We've just hired [info]marksmith as a developer, [info]deveiant will be rolling into town in the next few days, and [info]whitaker and I will soon follow. We will have more developers than ever available at the office, which is one of our big goals for 2004.

We haven't received the final versions of our last two commercials yet, as they keep being revised and re-edited. We'll make those available to download as soon as the production company is finished with them.

To finish addressing all of the questions & concerns for this year's State of the Goat, I've compiled all of our answers on this page. If you had a question you don't see on that page, feel free to leave me a comment or an email and I'll update it in the next round of answers.

The big development project for the past month was enhanced security for the entire site, using SSL and challenge/response authentication. Most of the issues that arose from the additional security have been ironed out, but as always feel free to report bugs to our support department. Also, [info]xevinx finished his new S2 style called Opal, which is currently available to paid users. You can see it in action on Kevin's journal, and can select it from the Customize Journal page after you select "New System (S2)" as your style system.

One of our big goals for February is to split up the overloaded concept of "friends", turning it into separate categories relating to who you read on your friends page, who you trust to read your entries, who you know in real life, etc. This will allow us to cluster this information and put it into memcache, so we'll be freeing up system resources along the way. [info]mahlon's working on merging our photo hosting site with our paid account service, and posting by camera phone will shortly follow. [info]lisa, [info]nbarkas, and [info]bradfitz will be working on upgrading our database servers, making sure each cluster runs faster and smoother.

Update: We are now selling a limited amount of hooded sweatshirts and baseball caps in the LiveJournal store.

Hope you all have a good February!

Password Scam

Monday, Jan 26th, 2004 -- 1:59 pm

jproulx
Currently we're seeing a number of abuse cases that describe accounts being broken into and used to spam communities, after the owners of those accounts entered their username and password in a form that was posted in various journals. The form claims to be a way of customizing your LiveJournal account. It's not — it's a password collection script.

Please never, ever give your password to anyone for any reason. LiveJournal will never ask you for your password via email, or for any reason other than to log into LiveJournal. You should never enter your password into a form on your friends page, or on a site that doesn't belong to LiveJournal.

If you are interested in customizing your journal, see the LiveJournal FAQ, specifically the "Customization" category. If you've entered your username and password into a form like this, please change your password immediately.

Enhanced Security

Friday, Jan 2nd, 2004 -- 5:34 pm

bradfitz
As we mentioned in yesterday's State of the Goat: 2004 (which you should read, btw! :-)), we now support secure logins and password changes.

This is especially important with everybody increasingly using wireless networks, which are usually unencrypted. You don't want your passwords flying around unprotected over the air!

The two new security available are:

SSL
We now use SSL (encryption) not only for payment processing, but also to let you create new accounts and change your password: the two pages that would otherwise send your password across the net in the clear.

Challenge/Response
If your browser supports JavaScript (almost all do), then the login page won't send your password in the clear either. Instead, the server sends a "challenge" which your browser combines with your password with JavaScript and generates a "response" which can't be reversed. Your browser then sends that (instead of the password) and the server checks to see if the result is what it expects. If your browser can't do JavaScript, you can alternatively log in via SSL instead, and the interface will give you a link to do so.

All of this will happen automatically, so don't worry about doing anything special. If you have questions or find problems, contact support and we'll help you out.

Enjoy!

(P.S. We'll be supporting HTTP Digest Auth and challenge/response in the interface handlers soon, too.....)

State of the Goat 2004

Thursday, Jan 1st, 2004 -- 3:03 pm

jproulx

Happy New Years! It's 2004, and time for another State of the Goat Address!

Wrap-up from State of the Goat 2003
Last year we mentioned hiring some new employees ([info]denisep and [info]ryanfitz). They're still with us, and we've picked up some more throughout 2003: [info]lisa got the sysadmin job we posted about and started shortly after the last State of the Goat post. [info]nbarkas is also doing sysadmin stuff, and he started about mid-year. Those two are both in Seattle, with all the servers. In Portland we've picked up [info]markf to work on the support and abuse departments and [info]mahlon as a programmer. [info]whitaker is still programming part-time while in school, but he'll probably go back in the summer to full-time again. [info]xevinx was hired to do web design and styles and graphics and lots of pretty things (like this network chart), and [info]daveman692 is doing an internship from a local high school. [info]deveiant is in Colorado writing code, and I'm stuck in PA for the time being, but we both have plans to move to Portland soon. One of our minor goals for 2004 is to have most of the employees working in the same physical location, which'll be nice.

Another goal of ours for 2003 was performance, which we feel we've improved on quite a bit. We developed memcached, which we're now using like crazy (even other sites across the net are starting to use it, like Slashdot and Wikipedia). Even though we've come a long way, we haven't gotten it perfect yet. Things fly most the time now, but there are occasional glitches. Our goal for 2004 is reliability: we want to be consistently fast, even if a bunch of servers crash at once. In [info]lj_backend we talked about our new master-master DB setup which we're starting to reconfigure everything to use. Over the next few months we're working on shuffling users around between DB clusters and upgrading old hardware and setting machines back up in the new config.

Moving on: we talked about S2 beta testing last year (our new style system). There are a few things that aren't complete, pages that aren't customizable (like the "your comment has been posted" page), but it's largely done. [info]xevinx and I have been making new styles for all users, and we'll continue to do so throughout 2004. We also might sponsor an S2 design contest like we did for the old style system.

And finally, we talked about wanting to remove invite codes, which we just recently did. It feels so good now. All the work that led up to that was really nice, too: moderated communities, screened comments, community invites. It's all stuff that lets people have more control over their account.

Highlights of 2003
Lots of events and new features happened in 2003 which we didn't foresee at the beginning of last year:

Questions addressed
I recently asked people if they had anything they wanted address for this year's post. Since we've only given you a limited time to comment (and in that time have garnered a healthy number of replies), we'll be answering all of your concerns in another news post in the near future. However, here are some of the topics that caught our eye:

What is the status on some of the much talked about projects like journal statistics, photo-hosting, etc?
Photo hosting: We have disk space and bandwidth handled now, so we just need to do quota integration since both fotobilder/picpix and LJ have their own system. We've already integrated the different systems' authentication methods via modules for the two services, so it should be a fairly easy task.
Statistics: Nobody's working on it, but it'd be nice. we really need more manpower or hours in the day.
How far along is S2? What's left to do, and what will we see from it?
S2 is pretty much done. We're happy with what we've done so far, but we can see what is left to finished. We need a lot more decent styles, and we need to start helping translators translate the styles, since that's one major thing that S2 supports that S1 doesn't.
Do we plan to sell more permanent accounts? When?
There are no current plans to sell more. It's a delicate issue: we don't want to sell them too cheap, or too expensive, and finding the right number to sell isn't easy. Although selling more permanent accounts isn't entirely out of the question, we don't have any plans for another sale.
Will we start to purge deleted accounts more frequently? Do we plan to delete inactive accounts? How will we handle namespace pollution?
That's one thing about our new master-master DB setup that's nicer: we can perform mass deletions much safer and do optimizations on the database that's offline in the pair. We'll start doing that in the next few months. As for inactive accounts, we have a plan outlined in [info]lj_biz.
What's the current climate around encouraging people to buy paid accounts? Are we going to see really compelling new features, or free-user limits in the next year? Or is 5% paid accounts an acceptable rate?
We don't want to limit or bug free users, coercing them to upgrade. Our plan is to offer enough fun stuff to paid users to make people want to pay. 5% paid accounts includes the inactive accounts. If you look at active accounts, about 10-12% of users are paying, and that's perfectly acceptable. Those 10-12% pay for everybody else just fine, and the site doesn't have any financial problems. We spend money very conservatively and make sure we keep spare money around "just in case".
What were the real cost of the commercials, and what effect will that have on the service?
Brad has written a reply concerning this in [info]lj_biz

Plans for 2004
Things we're interested in working on this year:

  • Secure logins and password changes using SSL and challenge/response (This is now live on the site)
  • Reliability improvement, mentioned above and in [info]lj_backend
  • Photo hosting (we have the hosting portion already written, now it's a matter of integration)
  • Posting by camera phone (waiting for the photo hosting)
  • Subscribe to get email/other notifications on any type of event: comments in any thread/journal/action. (ESN system)
  • Raw data access, fetching comments and downloading your entire journal
  • More new S2 styles
  • Increased interoperability between LiveJournal-based websites (opt-in roaming authentication, separate namespaces)
  • RSS and Atom syndication improvements

As usual, we'll be posting about these goals here in [info]news as the year progresses.

Have a Happy New Year!

Livejournal Commercials take 2

Wednesday, Dec 31st, 2003 -- 12:47 pm

lisa
We've got another commercial for you, this time with 2 download options. It's available in a smaller (lower resolution) format in mpg, as well as a larger (higher resolution) format in mpg available via BitTorrent.


High-Quality versions (BitTorrent)
Use the file-swarming technology "BitTorrent" to download these large files from tons of other people all at once. You'll get a faster download and it saves LJ from higher bandwidth costs, allowing us to make the large files available to you.
Commercial 2 (LJ Friends) and Commercial 1 (LJ Publishing).

Those choosing to use BitTorrent for the download of these files should be sure to leave the program running after the download is complete- to allow others to download from you.

Small versions (HTTP)
These small, low-quality versions should work on all computers: Commercial 2 (LJ Friends) and Commercial 1 (LJ Publishing).

LJ Publishing is the version Brad posted Monday. These are just 2 of 4 commercials that were purposefully made to be entirely different to appeal to various audiences. We will post the remaining 2 over the next week.

Be sure to keep watching this community for the State of the Goat address tomorrow.

[ << Previous 5 ]

English • Español • Deutsch • Français • Русский • →