Automating Journal Entries for Dreamwidth

Written on November 29, 2016

Last night, I was awake and thinking about how to create a community site on Dreamwidth. I wanted to post live updates regularly but wasn’t sure how to do this. Thinking back to what was done in the past, I was able to generate websites using Jekyll and Bash to pull information from an API to post static-sites of videos online. This allowed my company to seem like it was constantly updating its website when in reality it was a machine doing the work. This required some manual administration (such as running the machine and script); however, it ran mostly by itself and be re-implemented with the right staff.

Next I was able to create an RSS parser that grabs feeds, inserts them into a document, and then formats them. This project was dropped because to go further, I was required to make a Google application, which time did not permit.

Looking at these two projects, I could combine them to create software that would automate journal entries. I could post RSS feeds, link lists, and scheduled posts all from software on a computer.

Problem: Dreamwidth does not provide a way to automate entry posting, nor does it allow for scheduled posts.

Solution: Third-party software that uses parts of JLJ to schedule journal entries for both unique and automatically generated entries that include “RSS feed compilations” for easier “link-list” blog posts in communities and elsewhere on Dreamwidth.



User creates document. Document is saved within queue folder. Publication dates are pre-determined and software empties queue folder according to when time passes with daemon. Otherwise by default, queue folder is emptied routinely by either system or daemon. For RSS entries, document is created prior to queue empty. Document file is then compiled for publication. Such entries may be either formatted as articles of a newsletter, shortened articles, or linked lists. They are then sent out to DW for publication.


Security will need to be upgrade. Currently the software does not go through any secure channel to publish posts. This means all private posts would essentially be seen publicly somewhere online.

Take me home.

Check out the archive.