<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p>It's been a long time since we at Rad Inks last made a release of the <a href="http://www.radinks.com/sftp/" mce_href="http://www.radinks.com/sftp/">Rad SFTP Applet</a>. When it was first released it was a ground breaking applet and was even featured on the official java website. Since then it was overshadowed by <a href="http://www.radinks.com/upload/" mce_href="http://www.radinks.com/upload/">Rad Upload</a> and we have been putting more effort on the latter and not enough on the former. Finally we pulled up our socks and made a new release.</p>
            <p>The Rad Inks Secure FTP client makes use of the SSH FTP protocol, which despite the similarity in name with the File Transfer Protocol is a much more secure system. FTP is totally insecure. With FTP all the data and commands are transferred between the client and the server in plain text. Thus with FTP user names and passwords are transmitted without encryption. Surprisingly many people don't realise this. Security conscious webmasters and organizations are moving away from FTP and embracing the more secure SFTP where all the commands and data are transferred with encryption.</p>
            <p>Because the Rad SFTP applet runs with in the web browser an end user of the system does not need to install any software on his own computer. Because the applet is light weight it starts up almost instantly. It can rival the start up speed of a desktop client.</p>
            <p>In this new version we have added a new menu bar which can be switched on or off. It kinds of looks like an javascript/css menu but it isn't it's part of the applet itself. Resuming an interrupted transfer is a lot easier and we now provide an option to disable the host key check. The host key check is an essential part of an security conscious software but some end users are confused by it so at times it may be better not to display the host key confrmation dialog.</p>

        </div>
    </div>


</body>

</html>

Secure FTP

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>Rad Inks, has released a new improved version of Rad Upload; a drop in replacement for HTML file upload forms. If you are a regular visitor here, you will know that Rad Upload is the best way to upload a file to a website. If you want to read more about it, please take a look at the <a href="http://radinks/press/upload-feb2007.php">press release</a> or the <a href="http://www.radinks.com/upload/file.php">change notes</a></p>
            <p>With Rad Upload you can have multiple concurrent uploads going. That's something that many users liked but a few webmasters didn't appreciate it. They only wanted single thread. We heard them and it's now possible to restrict the user to one upload at a time. That's done by embedding the progress monitor inside the applet area. With the progress monitor occupying the drop area the applet will be unable to respond to any more drop events. When the ongoing upload is completed the applet will revert to the previous state and you can start another upload.</p>
            <p>What else have we changed? well we have made it a lot easier to configure, and we have added to entirely new progress monitors to keep the old ones company. Until now, the free version was equipped with only one monitor, but all four have been made available in the free version as well.</p>
            <p></p>

        </div>
    </div>


</body>

</html>

Get rid of your file upload form.

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>Much has been said about Adsense relevancy. Here is an example:</p>
            <p></p>
            <p></p>

        </div>
    </div>


</body>

</html>

Adsense Relevency.

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>Google loves Safari and Safari loves google. But google changes lovers too often for comfort. On the other hand, Safari is head over heals. So she is going to end up heartbroken. The big brother is the default search engine for the Safari browser on OS X. Safari is so loyal that the search box in the tool bar has just the one search engine. It cannot be changed without resorting to hexedit.</p>
            <p>Yahoo on the other hand hates Safari. It's more accurate to say yahoo hates OS X all together. Yahoo chat for example is not available for OS X, Hey wait a second gtalk isn't available either but ichat supports jabber, so that means you can use it with GTalk.</p>
            <p>The new Yahoo mail sounds very exicting, it probably is exciting too but not if you are a Safari (or even a Camino) fan. So what's the solution? set your default search engine in OS X to be firefox.</p>
            <p></p>

        </div>
    </div>


</body>

</html>

Safari - Google loves it Yahoo hates it.

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p><a href="1128.html">The other day</a>, I was scratching around trying to install the iterative refocus plugin for <a href="https://gimp.org">GIMP</a>. The errors were many. After fixing many of them, I came across what looked like an insurmountable error related to a missing library. Well the libraries are there, they were installed using <a href="http://fink.sourceforge.net/">fink</a> and can be found in the /sw/lib folder. Unfortunately the linker only looks for them in the /usr/local/lib/ folder.</p>
            <p>A partial solution was found on the fink FAQ. They suggest moving /usr/local/ out of the way. That's only a partial solution. gcc continues to ignore the -L directive. So I made symbolic links in /usr/local to the /sw/lib and /sw/include directories. The installation then progressed a few steps further before screeching to a halt again. This time the sand in the grease was provided by some pango packages.</p>
            <p>I installed all the pango packages along with freetype and libintl but the make system still insisted on looking for libintl.3.dylib instead of libintl.dylib. I made another symbolic link (clutching at straws now). Predictably it fails.</p>
            <p></p>
            <div style="margin-left:15px; color:#330000">
                <p></p>
                <p></p>
                <pre>gcc  -g -O2 -Wall   -o refocus-it  main-cmd.o getopt.o getopt1.o ../src/librefocus-it.a -lm -lm<p></p><p>/usr/bin/ld: Undefined symbols:</p><p>_bindtextdomain</p><p>_gettext</p><p>_textdomain</p></pre>
                <p></p>
                <p></p>
            </div>
            <p></p>
            <p>locate told me that libintl.3.dylib file is a part of the gimp libraries. So I created a symbolic link (still don't know why the linker doesn't look for the libraries in the right place)</p>
            <p></p>
            <div style="margin-left:15px; color:#000033">
                <p></p>
                <p></p>
                <pre>sudo ln -s /Applications/Imaging/Gimp.app/Contents/Resources/lib/libintl.3.dylib libintl.3.dylib</pre>
                <p></p>
                <p></p>
            </div>
            <p></p>
            <p>That didn't make the problem go away. In the end I decided to edit config.h and removed the #define ENABLE_NLS and #define HAVE_SETLOCALE lines. That cleared up the compilation problems!</p>
            <p>Hopefully make install will not produce any errors. It didn't. But why did it place the plug in /plug-in/ folder instead of in the /Applications/Imaging/Gimp.app/Contents/Resources/lib/gimp/2.0/plug-ins as it should? After all I have been through, it's a simple matter to push it there. Now comes the million beer question: does the iterative refocus plug in actually on my macbook? yes.</p>

        </div>
    </div>


</body>

</html>

Refocus it.

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>The RAW versus Jpeg religious debate continues to rage. I don't believe in any religion and I have had a chance to see both sides of the coin since getting my D70S. I started off shooting nothing but jpegs. Even experimented with the various bracket settings. <a href="959.html">Then someone threatened to hit me with a stick</a>, if I continued to shoot jpegs so I decided to try my hand at raw photography.</p>
            <p>After shooting a few hundred NEFs I gave up on it because <a href="971.html">processing raw photos on linux is such a pain</a>. Heck, Konqueror cannot even show you thumbnails of these pictures. Then in December, <a href="1097.html">I got a macbook</a> and tried processing RAW photographs on it. It's a sight easier than on linux but that's only becaus I have been using Lightroom. Lightroom is still in beta and it's not available for linux. To make matters worse, it's not open source! But I have a feeling that I will end up buying a copy when the start selling it.</p>
            <p>Even though working with camera raw is a lot easier on the macbook than on linux, In the end I decided not to take any sides in this debate. Both formats have their pros and cons. It's a just a matter of choosing the right horse for the right course or choosing the right format for the right light conditions.</p>
            <p>When the light is very bright so there is no light to speak of, I switch to raw. If I am shooting indoors, or when the light is just right I always capturing JPGs. When starting off with an empty CF card, I will more often than not capture NEFs because space is not a worry. When running out of space, I switch to Jpeg no matter what the light conditons are. I have never been good at flash photography so if I have to use the flash, I shoot raw.</p>
            <p>Sometime I forget to switch and capture Jpegs when I wanted NEFs and vice verce. But it doesn't really matter. Camera raw allows you to make big changes to white balance, exposure and some other settings without obvious distortion, Jpeg allows you to make small changes without artifacts or distortion showing up. But the key is that you shouldn't have to make drastic changes to any of the settings because it simpy means you haven't shot a good photograph in the first place. The best way to adjust such photos is with the delete button.</p>
            <p>If you want to see some of my photos please visit <a href="http://photos.raditha.com">photos.raditha.com</a></p>
            <p></p>

        </div>
    </div>


</body>

</html>

Monthly Archives for 2007 02

Secure FTP

Get rid of your file upload form.

Adsense Relevency.

Safari - Google loves it Yahoo hates it.

Refocus it.

Raw vs JPeg.