Stumpy Version 1.5 is Now Available!

Stumpy Version 1.5 is now out and ready for testing.
Should be functional, but please submit any issues you might find to the issues page.

Changes include (from commits):

  • Removed hardcoded domains from JS. We now pipe in through the stumpy_domain var by setting a global JS var ‘DOMAIN’ in the index and then reference that JS var in our scripts. You will no longer need to set your domain as hard coded into javascript code.
  • Updated to use get submission of new URLs for shortening. This should work, but needs to be tested on the production version to make sure WSGI and such are working okay without the earlier hack that was implemented.

Mutaku on Google+ Pages

We are now on Google+ Pages as you can see by way of the link on the right side of the page or by clicking here.

If you are a G+ user feel free to swing by the page. Will post software updates and anything Mutaku related to that page as well as to the other regular locations.

Happy G+ing!

We are back at Mutaku is now fully transitioned to the new site. Today, the old blue and white Mutaku came down and up went the new. It was a little sad to see all those years bzipped away, but all for the better.

It appears that all the bugs have been quashed and everything is running nicely. I am still working on filling in the gaps with some of the pages, and some others may get moved around a bit until everything falls into a groove. However, for the most part, what you see is the new and improved Mutaku; a Mutaku for a new era.

If you spot anything afoul, or have any ideas regarding what you wish to see here, please feel free to contact me.


Mutaku on GitHub

After endless peer pressure, Mutaku is finally on GitHub. I have to admit, initially I didn’t really see why I would need a version control system, let alone use something like GitHub. But 10 minutes into using, I was sold on both fronts.

Mutaku GitHub page

So head on over to the Mutaku GitHub page and feel free to follow and subscribe to the activity feed.

I’ve already thrown up one project that I was starting to get together to post here at the site. I will be working on gathering together some of my other projects to post as well with the goal being to have snapshots of all the Mutaku code and projects accessible publicly on GitHub.

Statistics from Mutaku of Yesteryear – Reminiscing

With the new site coming into it’s own, I thought I would do some reminiscing. Looking back over some of the old Geeklog statistics (the old CMS), I felt it might be fun to repost some of those things here before they are lost to the infinite abyss of the interwebs. These are obviously not quantitations to brag about or send a note home regarding, but it’s still fun to check out.

For those that didn’t frequent the old site (almost everyone else on the internet besides myself), Mutaku ran on the Geeklog CMS code. While keeping it’s generic, out-of-box, look, the code itself became heavily hacked up over the years. Accordingly, it was hard to leave it behind. It felt like ditching that reliable car you’ve had for so many years for something new and shiny and popular. I still feel like a bit of a turncoat.

But, here we are. New beginnings with a fresh look and a different take on life. Back then, it was hard to find interesting projects to do, let alone write about them. Nowadays, there are far too many things going on. Some exciting and fun, others mundane but necessary. Yet, all are interesting in their own light. That’s life.

Statistics? Oh yes, the old statistics from Geeklog. I lost my train of thought there for a second [Sitting in my rocking chair on front porch hanging from my mouth a single, bowed length of wheat the color of a day slowly fading into the oblivion of time past].

Site Statistics

Site Statistics
Total Hits to the system 1,131,114
Number of active users 1
Stories (Comments) in the system 66 (12)
Polls (Answers) in the system 3 (66)
Posts deleted as spam 26,714
Static Pages 3

Top Ten Viewed Stories

Story Title Views
Flash and Java on 64bit Ubuntu and Kubuntu 15,418
Build Your Own Jabber Server for Private Communication 11,828
Adding a New Hard Drive to Slackware Server 8,289
Cook your RAW photos into JPEG with Linux 6,683
Smart Boot Manager – An OS Independent Boot Manager 6,501
USB Drives in Slackware 12.0 5,200
Setting Up Thin Folding at Home Clients 5,184
Setting up a linux dialup connection 5,098
Retrieve WAN IP from LAN or Remotely 5,041
Gallery Remote Install Troubles : “nawk: error…” 3,972

Top Ten Emailed Stories

Story Title Emails
Ventures in upgrading (k)Ubuntu: Fix DVD Playback and Locale Issues in (k)Ubuntu 8.04 27
Flash and Java on 64bit Ubuntu and Kubuntu 9
Build Your Own Jabber Server for Private Communication 7
Smart Boot Manager – An OS Independent Boot Manager 4
Setting up a linux dialup connection 3
Backing up a personal DVD 3
Retrieve WAN IP from LAN or Remotely 2
Netflix Now Exclusively Bluray 2
Daily Links Edition v2.10.08 2
Adding a New Hard Drive to Slackware Server 2

Cook your RAW photos into JPEG with Linux

NOTE: This is a ported post from the old Mutaku site. Original post information:
Thursday, August 14 2008 @ 04:50 PM EDT Contributed by: xiao_haozi

Shooting in RAW format is great for the photography buff. However, when it is time to share with others, post on your photo gallery, or print at the local photo printing shop, you want something more portable. Here we’ll look at converting RAW photos (specifically Canon’s CRW format) into JPEGs using a batch command-line approach in BASH.

We will be using two tools to do our batch conversion:

1- DCRAW (available here)

2- CJPEG (available here)

CJPEG is part of the standard JPEG library (libjpeg) so you should already have that installed. If not you can find the source here and built as such:

./configure --enabled-shared
 make install (as root, e.g. sudo make install)

DCRAW is available here and can be built as such:

tar xzvf dcraw-8.87.tar.gz
cd dcraw-8.87
make install (as root, e.g. sudo make install)

Now that we have the prerequisites out of the way, we can try it out. We’ll manually do the conversion to ensure it works. Make sure you then compare the images and ensure they meet your needs/desires with the settings we use below.

In our example we will assume we have a directory called trip08 on our user’s desktop that contains some CRW raw images as well as others. We will go into this directory, make a CRW directory to copy our RAW images to for converting, search here and all subdirectories for CRW files and copy to our new directory, and then convert them using the two tools above so we will have in our new directory a copy of the original RAW CRW image as well as a new JPEG version.

Here we go:

cd ~/Desktop/trip08 && mkdir CRW_conversions
find . -name \*.[Cc][Rr][Ww] -exec cp "{}" CRW_conversions/ ";"

First, we went into our trip photo directory and made a directory called ‘CRW_conversions’ that we will work within. Next, we looked in the current trip directory (and subdirectories) for all files that end in ‘.crw’ including and variations on capitalization. The files we found are transfered to our CRW_conversions directory.

cd CRW_conversions
for i in *; do dcraw -c "$i" | cjpeg -quality 100 -optimize -progressive > $(echo $(basename "$i" ".crw").jpg); done

Now we went into our CRW_conversions directory that contains copies of our RAW images. We then constructed a loop which:

1- for i in *; do for each element in this directory do the following
2- dcraw -c “$i” | use dcraw to decode the element and pipe it out
3- cjpeg -quality 100 -optimize -progressive > accept the pipe from dcraw with cjpeg and convert to 100% quality jpeg with optimization and progressive processing and output that
4- $(echo $(basename “$i” “.crw”).jpg) take that output and put in a file called element.jpg where element is the name of the original CRW version without the extension ‘.crw’
5- ; done finish the loop once the iterations are done

We should now have a directory called CRW_conversions in our trip08 directory that contains copies of all our RAW images as well as fresh versions of each in JPEG format. The settings we used to convert have given us fairly high quality images that are still relatively large, so you may wish to alter these to your liking. You can do so by altering the CJPEG part of the conversion and find the options here:

man cjpeg

If you find that you have errors of ‘Empty input file’ and resultant JPEG files that are 0 bytes in size, you most likely have left out the ‘-c’ switch in your DCRAW part. This is needed to send the output with the pipe, or else you will end up with PPM files.

You can place most of this code into a shell script to do the brunt of the work for you without having to type in each time. We are currently working on a Python version which uses Tkinter to provide a GUI interface as well as options to convert and manipulate several image formats and will post source code and a how-to once it is finished. However, if you want to try out a shell version now you might want to try something like:

#!/bin/env bash
# crw2jpg                                                           
#      convert canon raw into jpeg                       
mkdir CRW_conversions
find . -name \*.[Cc][Rr][Ww] -exec cp "{}" CRW_conversions/ ";"
cd CRW_conversions
for i in *; do dcraw -c "$i" | cjpeg -quality 100 -optimize -progressive > $(echo $(basename "$i" ".crw").jpg); done

This is a very basic script without any real error control or logic, so add to it as you wish/see fit. If you wish to keep as such, you should just make sure that you don’t already have a conversion that was run in the existing directory. To run this:

#(copy the above script)
nano ~/bin/crw2jpg
#(paste and save)
chmod +x ~/bin/crw2jpg
cd to_directory_with_new_photos/

Enjoy cooking those RAW images, and be sure to check back for our conversion GUI. Good luck!