Megaupload’s FAQ states – “While you can use any of the major download managers, we recommend that you use Mega Manager instead.” Partly true.

With most other file hosting services, you just put in your login/password into your download manager, paste your list of links and that’s that.
This approach with Megaupload, on the other hand, will download html codes instead of actual files – even with the “Direct downloads” option selected in your account settings.

This leaves us with two options -

1. Either use “Mega manager”. Ugh ! Or …
2. Use the method described below (even though it involves a little more work than usual)

I found several articles discussing this on the internet, but all of them involve generating the actual download link in a browser and putting this link in the download manager – one file at a time (e.g., using Flashgot).
With the method described below, you’ll be able to queue your link list with minimal effort – no browser required!

For our preferred download manager, we use the same technique that Mega manager uses -

1. Login to Megaupload premium account using Internet explorer.
2. Go to your cookies storage folder (Run -> cookies for XP, C:\users\<username>\AppData\Roaming\Microsoft\Windows\Cookies for Vista/Win7)
3. Locate and open the megaupload cookie file <username>@megaupload[x].txt (x would be some number)
4. This file contains your username/password hash. Within its contents, look for the part that looks something like this -
   …<lot-of-crap-here>user<32-character-user-password-hash>megaupload.com<some-more-crap-here>…
   Make a note of this <32-character-user-password-hash>
5. To download megaupload links with any download manager, we need to modify the link like so -
   original link -
   http://www.megaupload.com/?d=UXP1JGLK
   modified link for download manager -
   http://www.megaupload.com/mgr_dl.php?d=UXP1JGLK&u=<32-character-user-password-hash>

You need to do steps 1-4 only once.

For step 5, you can use the attached excel to covert normal megaupload links into links usable in your download manager.

Please note that the <32-character-user-password-hash> is the hash of your unique username/password combination – sharing it is equivalent of sharing your username/password. (which, in case you didn’t already know, is in violation of Megaupload’s terms of service, and can lead to your premium account getting blocked).
p.s. – Please leave a comment if it worked for you !

I’m going to talk about the one that worked the best for me – the one using symbolic links.

I had on my hands multiple blogs each with different owner/author and different databases.

All I had to do was -

1. put all standard wordpress files into a directory above the level that the individual blogs were located – these files will now be shared by all blogs (make sure the path’s accessible to php for includes)
2. remove all standard files/folders (except wp-config.php) from each of the individual blog’s docroot
3. in each individual blog’s doc root, create symlinks pointing to all standard files & folders within the shared wordpress directory.
4. add to the each individual wp-config.php the following line -

   define('ABSPATH', dirname(__FILE__) . '/');

5. in the shared wp-load.php, change -

   define( 'ABSPATH', dirname(__FILE__) . '/' );

   to read -

   define( 'ABSPATH', $_SERVER["DOCUMENT_ROOT"] . '/');

the directory structure of each individual blog’s docroot looks like so -

If you wish to share a few plugins and themes, but keep a few different plugins/themes on different blogs, this can be done in the same way.
In each blog’s doc root, don’t create a symlink to the whole shared wp-content. Rather symlink the individual plugin or themes folders instead.
like so -

It may be a good idea to have all plugins/themes inside the shared wp-content instead of in individual blog’s wp-content, and symlink them back into individual blogs as required. This makes updating the plugins etc. easier. (I share all-in-one-seo-pack and google-sitemap-generator across multiple blogs)

Now to update wordpress (for all the blogs), just extract the new wordpress files overwriting the shared wordpress directory!
The shared plugins can be updated across the board in the same way !

This blog is now running with this hack, leave a comment if you notice something not working correctly. (I tested and found comments to be working fine )

p.s. – The shared wordpress files are owned by root and are not writable by individual blog, and security is maintained by suexec’d php.
This might mean that plugin installation/update might now work from within the wp-admin area’s UI. You’ll have to do it from command line.

Dropbear is a lightweight SSH server and client . It implements SSH2 protocol, just like OpenSSH, but without all the bells and whistles. So much so that it doesn’t even come bundled with SFTP capability.
But we can use the SFTP server that comes bundled with OpenSSH to work with Dropbear.
Let’s begin -

It’s always a good idea to update & upgrade your installation first -

:~# apt-get update
:~# apt-get upgrade

First we need to install OpenSSH, if you don’t already have it (only to use its SFTP server with dropbear) -

:~# apt-get install openssh-server

Now let’s install Dropbear -

:~# apt-get install dropbear

Dropbear gets installed, but it is disabled by default. To enable it, edit /etc/default/dropbear and -

modify the line -

NO_START=1

to read -

NO_START=0

You can optionally change the listening port (22 by default) by editing the DROPBEAR_PORT variable in the same file. It’s recommended that you do this, for enhanced security. Remember to also change the port number that you connect to in your SSH/SFTP client.

Now that we’ve enabled Dropbear, we need to disable OpenSSH.

:~# mv /etc/rc2.d/S16ssh /etc/rc2.d/K16ssh

finally -

:~# /etc/init.d/ssh stop
:~# /etc/init.d/dropbear start

Now, without closing your existing SSH connection, open a new SSH session and make sure your SSH client can connect and show you the username/password prompt. If it doesn’t work and you logout your current connection – you’ll be left without access to your server.
Once you’re sure it all works, you can logout and login again to end all OpenSSH processes, and let Dropbear takeover SSH responsibilities.
If you check your resource usage, before and after, you should be able to notice the difference now
Also, since we haven’t uninstalled OpenSSH, Dropbear will be able to serve SFTP with the OpenSSH’s SFTP server. This is located at /usr/lib/openssh/sftp-server , and symlinked as /usr/lib/sftp-server.
If you want, you can also backup the sftp-server binary, remove openssh-server package and put the binary back at /usr/lib/sftp-server – and dropbear will still be able to serve SFTP with it.

Now that Dropbear is up and running, let’s setup private/public key pair based passwordless authentication for the root user – it’s convenient and just as secure (if not more so).

Let’s generate a key pair for SSH use -

:~# ssh-keygen

the default paths are good for use with Dropbear.
Don’t enter a passphrase if you don’t want to have to enter it everytime you login to SSH or do SFTP.

Now we must authorise the generated public key for SSH use -

:~# cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys

and copy the private key to your local machine.

*hint* At this point, you can use SFTP to copy this file

It is now safe to delete the generated key pair -

:~# rm /root/.ssh/id_rsa
:~# rm /root/.ssh/id_rsa.pub

Now you can point your SSH/SFTP client to use the private key to allow password-less login.

If, like me, you’re using PuTTY (or WinSCP) – you’ll need to convert the private key to PuTTY compatible .ppk format.
To do this, download PuTTYGen.
Once you run PuTTYGen, select “Conversions” -> “Import key” and import the private key file.
Next, click “Save private key” and save the converted private key in PuTTY’s own format.
This converted private key can now be used with PuTTY client (Connection -> SSH -> Auth -> “Private key file for authentication”), and with WinSCP for passwordless login to SFTP.

Lastly, we need to disable password login for root in Dropbear. To do this, edit the file /etc/default/dropbear and -
edit the line -

DROPBEAR_EXTRA_ARGS=""

to read -

DROPBEAR_EXTRA_ARGS="-g"

and then

:~# /etc/init.d/dropbear restart

And we’re all done !

A lightweight replacement SSH server with SFTP and passwordless logins for root !
All with the usual ease of Debian and apt.

p.s. – You can use these switches in dropbear configuration -

• Disallow root logins -

  DROPBEAR_EXTRA_ARGS="-w"
  
  

• Disable password logins -

  DROPBEAR_EXTRA_ARGS="-s"
  
  

• Disable password logins for root -

  DROPBEAR_EXTRA_ARGS="-g"
  
  

• or any combination thereof, like -

  DROPBEAR_EXTRA_ARGS="-w -s"

From what I know of these two applications, I can think of the following (not thoroughly tested) ways of synchronizing your mailboxes in Thunderbird and Outlook Express :

Outlook Express to Thunderbird
If you have Outlook express and Thunderbird on different machines – Copy the Outlook Express mailbox files to the machine with Thunderbird at the corresponding path.

These files are located at – C:\Documents and Settings\<yourprofilename>\Local Settings\Application Data\Identities\{some-random-16-char-guid-here}\Microsoft\Outlook Express\

Now from within Thunderbird » Import » Mail » Outlook Express.

You may have to create an identical folder structure in the Outlook express of the machine that runs Thudnerbird.

Thunderbird to Outlook Express

Download and install SmartSave Thunderbird Extension – an extension that lets you export multiple mails in one go.

Right Click » Export (the folders/messages that you want to sync into Outlook express).

A bunch of .eml files will be created.
If you have Outlook express and Thunderbird on different machines, copy these files to the machine with Outlook Express.

Select all and drag these files into the corresponding folder inside Outlook express.

That is, the files from Thunderbird’s inbox into Outlook Express’ inbox; those from Thunderbird’s sentbox into Outlook Express’ sentbox and so on. (There’s no compulsion, but it doesn’t make much sense otherwise …)

If you find that the above doesn’t work for you or know of a better way of doing the same – let me know (you know where to leave a message)

To capture good quality video without sacrificing a huge amount of disk space, we must compress it before storing it onto the disk.
One popular codec for compressing video is the DivX codec.
It’s compatible with almost all video editing/capturing software.
DivX homepage
Download DivX

For video editing/capturing, I recommend VirtualDub.
Virtual dub allows editing/converting/capturing video files with a variety of professional features.
VirtualDub homepage
Download VirtualDub

First, you’ll need to install both these software.To begin Video capture, fire up VirtualDub, and select “Capture AVI” from the File menu.

Next We need to set the Video Capture source :

All “Video for Windows” (VFW) compatible video devices connected to your computer should be available here.Thus you can capture video from sources like webcams, TV tuners, camcorders … basically almost any device that works with a computer.

Next we set the location to save the created video file :

Now to set up video compression :

You can also optionally configure advanced compression settings for the selected codec at this point (Select “Configure” at this dialogbox).

If you have your devices’s audio output connected to your computer’s line-in input, you may also want to configure audio compression at this point :

That’s it !
Just hit “F5″ to start video capture, hit “Esc” to stop it.

Also note that if the device is not recognized by VirtualDub or doesn’t work with it for some reason, you can probably still capture compressed video using the software that came with your device.
Just look around for a option to set the compression codec for capture, and select DivX.