NTFS-3g is aviable in Debian unstable.
You can probably download and install the binary package from packages.debian.org, you can add Debian unstable and 'pin' yourself to Etch, or you can do a source code backport and compile.
I do this time to time when running stable when I need a newer version of whatever package I want to use. I did a source code backport for OpenAFS once since the OpenAFS version for Sarge sucked and it worked fine.
Simple pinning works fine and allows you to install binary packages from newer or older versions of Debian. The downside is that you can end up with a sort of horrible hybrid between stable/testing or something like that. Working with source packages keeps that to a minimum.
There are a lot of online stuff for doing pinning. All you realy do is add unstable sources and setup a /etc/apt/preferences file.
But working with source files can be more complicated. Here is what I did to install ntfs-3g in etch...
added:
deb******
http://<yourdebianmirror>/debian unstable main contrib non-free
to /etc/apt/source.list
(you'll want to create a work directory for this)
apt-get update
apt-get build-dep ntfs
(then I got a error about no aviable version of libfuse-dev so I need to pull that dependancy back..)
#grabs the build dependancies..
apt-get build-dep libfuse-dev
# grabs the source code
apt-get source libfuse-dev
# builds the packages.
apt-get -b source libfuse-dev
# installs the packages
dpkg -i *.deb
Now that I have the dependancies cleared...
apt-get build-dep ntfs-3g
apt-get source ntfs-3g
apt-get -b source ntfs-3g
dpkg -i *.deb
And that's it. If your using a tool called wajig it's even easier...
wajig build-depend ntfs-3g
wajig build ntfs-3g
dpkg -i *.deb
But that's pretty much it.
Using the apt-get commands it can also allow you to compile optimized packages or manually apply patches, a lot like Gentoo.
Then those deb packages are good enough you can just copy them from machine to machine or give them out to other people.
apt pinning is pretty simple also. It deals with binary files but it's not bad.
What apt-pinning is very good for is when you want to upgrade from stable to testing. That way you can setup mirrors for stable, testing, AND unstable and say testing has highest priority. This is usefull because often testing will have missing packages or whatnot that only are aviable in either stable or unstable. This way you can have access to everything and relatively easily pick and choose which you'd like.
Also it's nice if your running unstable, but you'd like to temporary upgrade packages to experimental versions.
I do this for Gimp, for example, because the development version of Gimp is much better then the 2.2 series.
edit:
Oh and don't forget to add your user to the 'fuse' group. This will alow you to use userspace file systems without root permissions.
adduser username fuse
then you have to log out and log back in for group changes to go into effect.