|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...
Ah, this argument. :)
This argument is more appropriate for say VB6 -- code there would not compile on anything but VB6.
Even here, there's some semantics involved -- if you publish the source, it's an open-source program but is not built around the traditional open-source model , where everything from code to compiler is available.
But, for .Net, the core .NET CLI and C# specifications have been published to ECMA / ISO. So, theoretically, anyone can create a .NET CLI and anyone can create a C# compiler.
This is what makes the open-source .NET CLI -- Mono -- possible. Microsoft does offer their own free IDE (VS 2005 Express) for C#, but there are also at least three open source IDEs - SharpDevelop, MonoDevelop, and Eclipse -- maybe there's more -- that can be utilized for the .Net framework, or in some cases the Mono framework.
So, it's not quite *fully* the open-source model yet, but especially considering Mono, it's pretty durn close. The main issue with this app in other environments would be porting it to get rid of Windows-specific GUI stuff, and other OS specific things. And actually that's a fairly common task on almost all platforms, open source of not. :)
When I get time, I'll probably look at playing with this software on Mono and see what modifications are needed... maybe even compile a Linux version of this using GTK# GUI routines for the heck of it.