February 20th, 2001


Empowering development

I am posting this because I wanted to point out a few important goals and ask a few basic questions.

Recently, a potential developer left their profile in the lj_biz talent pool. I obviously wanted to refer them to get an account in lj_dev and to help them towards developing with us, but I realized that we don't have any kind of link on the lj_dev page for becoming a member, or at least for the userinfo page of lj_dev. This should be fixed, since it is a obvious roadblock for people becoming developers at LiveJournal.

While I was at it, I wanted to ask a few obvious questions of all of you. We all know and appreciate how much hard work Brad has done over the last month or so to enable the LiveJournal development community to do their jobs... but what can we do personally to make it easier for you to develop for us?

There are 45 members of the community here and 78 people watching. Do any of you feel like you want to help out but don't know where to start or what to do? Is there anything that will assist you to become an active developer for LiveJournal that we have overlooked? Do we need to make the individual projects more accessible? Is there anything that we can improve from a site design/ usability standpoint?

This is fundamentally important... the more we enable people to participate in the development of LiveJournal, the better off everyone will be. There is nothing that we can do at LiveJournal that is more fundamentally important than enabling people to help us. From my perspective as a non-developer, it feels like we put too many barriers and roadblocks in the way of the people who want to assist us.

One thing that I am concerned about is that a lot of the tasks that LiveJournal developers are working on are led by just a single person. We need to make room for others to help out, whenever possible, and that means we need to create small teams who will work together on specific tasks. People who are currently LiveJournal developers should consider stepping into the role of a lead developer, and should use this community to create teams to accomplish specific goals.

I have created a lot of ideas for LiveJournal, and a lot of different teams and departments. My favorite method of handling these new projects has always been to work myself on some kind of basic implementation and then find someone who can perform the task I've created, train them to do the work, and let them take over, while I oversee what they do and offer assistance, as needed. Meanwhile, I move on to the next idea... Many of you could and should do the same. A big part of being a leader is finding, developing, and empowering talented people. LiveJournal developers should consider themselves leaders and always look for the chance to empower others to succeed. They should also consider themselves evangelists, and try to spread the word of what we are doing to their developer friends and to the open source community in general.

I have heard people criticize open source projects (and us in particular), saying that volunteer-run groups don't work and that it's easier to do the work yourself than to oversee a bunch of volunteers... that we should follow traditional business models if we want the kind of success with our software that traditional businesses have. I can assure you here and now that this is 100% pure grade-A horseshit. We have a community full of exceptional, talented people who believe in what they're doing and are willing to step up and take the lead. For those who have developed for us, I wanted to let you know that you are doing a great job and deserve a great deal of credit for the success of LiveJournal.

Ok, I've said my peace... now it's time for all of you to put in your expert opinions as to how we can make development work that much better and what we can do to really scale the size of our development. Let's get that feedback!


I think mod_backhand is a little buggy.

It has some problems forwarding cookies between servers when forwarding requests, but I can't track down exactly in what cases. A quick scan of their code shows that they really don't know what they're doing as far as headers that repeat multiple times (as cookie headers can). Also, they have a section in their session code that talks about cookies repeating multiple times and saying, "this won't work if multiple cookies are present, but it works in mozilla M18... let's hope everybody behaves like that". *sigh*

Anybody know mod_backhand? Anybody want to fix it? Anybody want to start a discussion on the mailing list about this issue?

I'm going to bed. More debugging tomorrow night.
  • genders

Did I Miss Something?

Everyone is complaining about their logins not sticking. Should we be collecting browser/cookie data again? Or is there some stock response that would be useful?

I don't know, it's not happening to me...
  • archon

LiveJournal.pm v1.0

This is the initial release of LiveJournal.pm. It is an object oriented
Perl implementation of the LiveJournal protocol. This release is protocol
complete, which means it should completely support all modes. There are
several methods that will be added in the near future for convenience.
This announcement is being made with the module. (=

There are still some design decisions I haven't finalized. See the TODO
file for more details. If you decide to use this module as your API,
please understand that some things are subject to change but I will
endeavor to make them as painless as possible. I myself will be developing
a perl/Tk GUI using this module so I have good reason to keep it relatively

At the moment, the biggest question is the name. There is already a
LJ::Client. For the time being, I am calling this simply LiveJournal.
Maybe LJ::Protocol?

Feel free to email me with suggestions, requests, bugs, tautologies, or
questions after you've read the documentation (; . Also, I would
appreciate knowing if you do use this module.

You can get a copy of the client here.

Patches welcome and happy LiveJournalling!
  • Current Music
    David Garza - Discoball World

Attention all MyLJ devs! :)


At some point in time, everyone who is or has been working on an LJ Sync client has seen some things return completely wrong from the server. If you have seen this on your client, would you please post a comment with some logs and details of what you were doing. AKA: What you requested, what you were expecting, and what you got back.

I would like to be able to use this entry as a reference point for all of the bugs in the sync system. If you have dicussed your bugs/issues with brad already, please comment with a link to the thread.

Please answer this as soon as you can, so that brad may fix the server-side issues and we can all get the MyLJ clients running and ... [deity] forbid, be USEFUL!
  • jwendl

Hey people its me a newbie

hello all

i just thought i would announce my presense in the prestigious lj_dev community.

i bring with me an offering of programming knowledge from several platforms and several languages.
i was kinda thinking about building a site like this
that was based on the idea of many members commenting on certain things that i post on it
(like anime etc.) then someone pointed me here and i feel in awe you guys have done an excellent job here and i devote my services and knowledge to the greater good of this site.

yea so what im bored at work right now lol anyways peace
  • Current Music
    Song - Killing In The Name By - Rage Against The Machine
my eye
  • foobar

LJ stats

Bizarre little idea popped into my head... how about a way to view some basic stats, graphed out?

I was thinking, for each month, week, whatever, generate a chart, showing posts per day, comments per day, perhaps a comments to posts ratio, maybe (if it's stored) friends added / removed per day, etc.

I thought of this because I was wondering earlier how my posting habits had changed; so I took 10 minutes and used the calendar to make a list of every day I had posted and how many, put them into excel, and graphed it. Then, to further satisfy my curiosity, I did the same thing with comments, and as a third column, (comments/posts)*10. (I don't get enough comments each day to have my ratio come anywhere near my actual number of posts ;) )

What point? None, really - but it was interesting to see. It was also interesting to see, when I had gotten quite ill for a few days, when Christmas came, when other events like that happened, how it affected my posts. It's all trivia and rather pointless, but interesting trivia, if you ask me.

Now, I know it'd take someone familiar with GD, or perhaps something like MRTG's graphing component (RRDtool or something, I forget, and which would probably be overkill, but...), to write a script to graph this sort of thing and generate it on the fly. I'm not overly familiar with either but reviewing them briefly it seems simple enough, albeit a bit of a cpu-hog. Maybe if they were generated periodically rather than on the fly? I dunno. Just a thought, anyway, figured it might be a fun little feature.