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.

Sun, 12 Nov 2017

A dedicated social blog?

I'm thinking that it's time for me to break out these social-style posts into their own blog.

I haven't done a hard analysis, but if I had to guess, I'd say I'm putting out 50 social posts for every traditional blog post. And since the social posts are in a subdirectory (aka a category), it's easy to go to that category and see all of the social posts, or see all the posts, traditional and social.

But there's no way to exclude the /updates directory and see everything but what's in that part of the filesystem. I'm sure I could code this into Ode, which is nothing if not flexible, but the more "natural" way to handle this is to have a separate blog for social posts, keeping this one for traditional, long-form writing.

It's an idea. The good thing about Ode and its flat-file structure is that I could move all of the "old" social posts into the new blog by simply copying the directory and its contents into the new site's /documents directory.

I'm not ready to do it just yet, but I am thinking about it. If I'm only putting out 10 social posts a day, I think a single blog is manageable for the reader. I am probably doing 25 some days, five on others.

So I may stick with the current arrangement (the preferred choice of the lazy), but another thing having two sites does is simplify the sending of posts to social-media sites. With two separate blogs, there would be no contortions to get traditional updates (post title and post link) automatically sent to Twitter with social updates (post body only) either excluded (I'm using my Blog Poster app to send them to Twitter) or sent automatically.