|LJ-Sec 0.1 now released
||[Jul. 14th, 2006|05:56 pm]
LiveJournal Client Discussions
I have decided to create a solution that allows you to mass-change your security settings. This is a dedicated client, and allows for more complicated security changes than simply switching public posts to friends only. It also acts as a journal archive in the process.
I called the program LJ-Sec.
It is open source (C#), of course. It's designed for Windows systems, and requires the .NET framework (1.1).
You can download the program, and optionally the source, here.
Here are some features:
Easily switch post group security levels (eg Public to Friends Only)
Perform more complicated custom selections
LJ-Sec automatically creates a journal archive, because that's the way the interface works. So you can preview your older posts too.
Search your archived journal (boolean search capability). You can tag the results as posts you wish to change.
Open source (C#).
This *is* an initial release, and while I haven't had any problems with post eating etc. in tests, I recommend backing up your journal with Livejournal's backup tool before using this program.
Hopefully you enjoy the program. :)
Any suggestions for future improvements will be appreciated. I've already noted that bulk find-and-replace might be a good thing to add to this in the future...
This looks pretty cool. I don't have Windows, so I can't try it myself, but I have a question: does it zap all tags? Because I have been playing around with the 'editevent' method, and it seems to delete all tags associated with the entry (unless, presumably, one finds a way to preserve them, which I haven't yet).
Tags (if I remember right) are one of the "meta-data" events available in Livejournal... this along with current music, current mood, and other items like this. In order to read this, you basically have to grab the prop_count value, and read each value in. In the XML-RPC interface, the props structure returned is where you will find this.
When posting, you basically (in flat file format) create a string that looks like property_name_1=property_value&property_name_2=propertyvalue... etc. XML-RPC, looks like you do something similar within the structure.
The actual property name isn't documented anywhere, it looks like, but the property name to use is prop_taglist if you want to set it.
Thanks. I'll look into this when I get a chance. Do you know if there is any way to tell LJ to simply preserve tags unaltered when doing an editentry? Because it presently seems to remove them if they're not explicitly mentioned in the xml-rpc editentry request.
Unfortunately, I don't know of a way to do that, sorry.