Title photo
frugal technology, simple living and guerrilla large-appliance repair

Regular blog here, 'microblog' there

Many of my traditional blog post live on this site, but a great majority of my social-style posts can be found on my much-busier microbloging site at updates.passthejoe.net. It's busier because my BlogPoster "microblogging" script generates short, Twitter-style posts from the Linux or Windows (or anywhere you can run Ruby with too many Gems) command line, uploads them to the web server and send them out on my Twitter and Mastodon feeds.

I used to post to this blog via scripts and Unix/Linux utilities (curl and Unison) that helped me mirror the files locally and on the server. Since this site recently moved hosts, none of that is set up. I'm just using SFTP and SSH to write posts and manage the site.

Disqus comments are not live just yet because I'm not sure about what I'm going to do for the domain on this site. I'll probably restore the old domain at first just to have some continuity, but for now I like using the "free" domain from this site's new host, NearlyFreeSpeech.net.

Sat, 31 Aug 2013

Proposal: A native commenting system for Ode

Level of difficulty: High

Description

Commenting for Ode is currently handled with a Disqus addin that integrates the popular hosted commenting platform with the self-hosted Ode system.

A native Ode commenting system -- also integrated via addin -- would either create its own text files, or add to existing post files, via a comment form that would appear at the bottom of individual entries.

Perhaps a native Ode commenting system could interoprate with Disqus, so a blog's Disqus comments could be converted to native Ode comments, and vice versa, like the way Disqus works with WordPress?

Notes and questions

  • Is there anything in Blosxom or Pyblosxom that could repurposed for an Ode commenting system?

  • Is there anything in the Chronicle Blog Compiler commenting code that could be repurposed for an Ode commenting system?