June 25th, 2005

  • oolonc

(no subject)

Hello, I'm a going to be senior-like at Some Tech School, I've been using livejournal for a while, and thinking about how I could help/improve this service. Experience includes (relatively small applications in) SQL, PHP, python, java, etc. I do have one question. We do exports of both entries(monthly) and comments(all) in nice XML formats. Is there any way that we could combine these services to make a complete journal backup? It could also be done relatively easily with a python script externally, I think, but I was thinking it would be nice to offer a complete backup function as a part of the service? Would this create bandwidth issues? Anyway, this is my idea and introduction. Nice to meet you all!

s2: logged in user

There doesn't appear to be any way to find out who is logged in and viewing a page through S2; there are viewer_logged_in() and viewer_is_owner(), but that's it if core.bml is to believed.

Is this policy to stop layer authors doing nasty per-user hacks, or is it something that can be addressed? It's not a major hassle, I'd just like to be able to put an LJ-page-stylee "Welcome randomuser [ Log out? ]" text on pages, in the same place as my soon-to-be-added "log in" link will go, when I decide where I'm going to put it.