Comments | djdigit: LJ Tool: posts grouped by security filter

djdigit

LJ Tool: posts grouped by security filter

Dec 07, 2006 18:20

I recently wanted to know to which security filters my historical entries were locked... but LJ doesn't expose this kind of view. The best you can do is visit each entry and check its permissions via its "edit" page. I looked for an existing tool to give me what I wanted, but couldn't find one... so I did what any self-respecting geek would do ( Read more... )

perl, geekery

Comments 5

djmermaid December 8 2006, 02:26:29 UTC

How awesome are you!

Too bad I am a Mac girl. But, what a great idea!

djdigit December 8 2006, 02:50:02 UTC

If you want, you can download ActivePerl for OS X here: http://downloads.activestate.com/ActivePerl/MacOSX/5.8/ActivePerl-5.8.8.819-darwin-8.7.0-gcc-267479.dmg.

Then you'd use the ppm (perl package manager) GUI to install HTML::Template and LJ::Simple and then just run the .pl script. But one of the beauties of Perl is that it's supported on tons of platforms... you just have to install it. It just turned out to be pretty easy to build up a single executable file for Windows that would save people from having to install ActiveState Perl to run it (I figured, otherwise, no one would actually get much use out of it).

Hope that helps (if you're really interested in getting the script's results)!

nancyblue December 8 2006, 02:35:20 UTC

Yeah, this looks really cool!

error getting data caladrius December 8 2006, 17:44:35 UTC

All I get is: Error logging in: Error in getting data from www.livejournal.com [204.9.177.18] - Unknown error

Does LJ::Simple->new() do anything that might be getting eaten by the firewall?

Re: error getting data djdigit December 8 2006, 18:02:50 UTC

Looking at LJ::Simple's source, that error is happening after the (HTTP) request has been sent and select() says the socket's ready for reading, but the sysread() had an error. The bit after the dash ("Unknown error") is $! (perhaps it's so unhelpful because it's Windows?).

AFAIK, it's a simple HTTP transaction to port 80 of www.livejournal.com, so I don't know how a firewall could interfere at the reading-the-response stage. A packet trace of the transaction might reveal more details, but off-hand, I don't know what the problem could be. :(