Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Social logging script for Day One
Ruby Python Makefile C
Fetching latest commit...
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Social logging script for Day One


Slogger indexes various public social services and creates Day One ( journal entries for them. It allows you to keep a personal journal that collects your online social life automatically, all in one place.


  • Slogger 2.x uses a plugin architecture to allow easy extension
    • Default plugins:
      • Gist (gists created in the last 24 hours. Title and description only, logged as a single digest)
      • Flickr (images uploaded in the last 24 hours, each as an individual post. Can handle multiple accounts)
      • (Scrobbled songs for the current day)
      • RSS feeds (designed to pull in your blog posts with leading image and excerpt (optionally markdownified). Handles multiple feeds)
      • Twitter (Tweets and Favorites for the day as digest entries, handles multiple Twitter accounts)
      • Foursquare (Checkins for the day)
  • Slogger can be called with a single argument that is a path to a local image, and an entry will be created for that image.
    • You can use this with a folder action or launchd task to add files from a folder connected to something like Any images added to the watched folder will be turned into journal entries.
      • Note that Slogger does not delete the original image, so your script needs to move files out of the folder manually to avoid double-processing.


  1. From within the Slogger folder, run ./slogger to create the initial configuration file.
  2. Edit the file slogger_config that shows up
    • The only options will be 'storage:' and 'image_filename_is_title:'
    • storage: should be set to either 'icloud' or a path to a Dropbox-synced Journal
    • image_filename_is_title: should be set to true or false. If true, it will use the base filename (without extension) as the title of images imported individually.
  3. Move plugins you want to use into ./plugins/, and plugins you want to disable into ./plugins_disabled.
  4. Run ./slogger again to update the configuration file with enabled plugin options.
  5. Edit slogger_config and fill in the necessary parameters for listed configuration settings.
  6. Next time you run ./slogger, it will execute the plugins and generate your log entries. Run it manually to test, and then automate it using Lingon (launchd) or other scheduling app.

Plugin development

Documentation coming. See plugin_template.rb to get started.

Something went wrong with that request. Please try again.