Evan Martin (evan) wrote in evan_tech,
Evan Martin
evan
evan_tech

ljfs

puppy:~/projects/lj/ljrb/sample% ./fuse ../../evan_tech.db lj
...
puppy:~/projects/lj/ljrb/sample% ls lj/2006/03/10
661.txt 662.txt
puppy:~/projects/lj/ljrb/sample% cat lj/2006/03/10/662.txt
gem for ljrb
============

Thanks to your advice, I have successfully made a gem and uploaded it to Rubyforge. So I guess it'll show up in the gems system eventually...?

Otherwise, you can download the tarball or gem from the <a href="http://neugierig.org/software/livejournal/ruby/">homepage</a>.

Please let me know if it works for you.


I was thinking of using this to make offline editing painless: I could make it so editing one of these files marks it as dirty in the database, and then I could make the "sync" mode bidirectional by pushing the dirty entries. But I dunno if it's worth it, and I'm a little concerned about the distributed revisioning problem: if it's edited on the server and on the client separately, how can the client know not to clobber your changes? (I guess it could retrieve each entry before allowing pushing new ones and verify the server-side one is as expected...)

Using fuse, at least through Ruby, is a little cumbersome: each method you provide (directory?, read_file) needs to validate all the paths provided. *shrug*
Tags: livejournal, project, ruby
Subscribe

  • dremel

    They published a paper on Dremel, my favorite previously-unpublished tool from the Google toolchest. Greg Linden discusses it: "[...] it is capable…

  • your vcs sucks

    I've been hacking on some Haskell stuff lately that's all managed in darcs and it's reminded me of an observation I made over two years ago now (see…

  • google ime

    Japanophiles might be interested to learn that Google released a Japanese IME. IME is the sort of NLP problem that Google is nearly uniquely…

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 8 comments