Found something useful? Don't forget to leave a comment!


Saturday, February 6, 2010

The Guide to Safe Torrenting: College Edition

The ubiquity and ease of use of the BitTorrent P2P protocol has attracted to it a countless number of users. But as with any P2P technology, it carries with it risks, especially in the context of copyrighted content. The MPAA, RIAA, and other so-called antipiracy outfits acting as mercenaries on behalf of content owners employ a variety of controversial techniques in an attempt to catch people downloading or uploading a torrent red-handed. The successful capture of a name, or more likely IP address can have some pretty undesirable legal consequences, particularly in the United States due to the Digital Millenium Copyright Act (DMCA). A cease-and-desist letter is usually sent, followed by a demand for a large, financially burdening out-of-court settlement. This threat is especially damaging on college and university campuses, where the user base is young and often ill-informed about P2P safety, not to mention poor! Furthermore, colleges and universities often have their own, equally undesirable sanctions should they have to forward a copyright claim letter to the student. The risk of being pursued for copyright infringement, however, can be significantly minimized if one knows how to keep a low surface profile on the network. Here are several tips and tricks that will help reduce the risks of using BitTorrent on a college network, or more generally, a high-risk environment.

  1. Refrain from downloading new, high-profile content in the days following its release
    Content creators and their hired copyright watchdogs are almost certain to be monitoring torrents of newly released movies and (possibly to a lesser extent) music and software. Don’t let the temptation of downloading a brand-new film screw you over – if you wait at least a week, the dangers of connecting to bad peers is significantly reduced.
  2. Limit your speed
    As with #1, it’s all about discipline, discipline, discipline. Is it really going to kill you to wait an hour or two extra to finish that torrent? If you’re maxing out your upload/download capacity for extended periods of time (especially likely if using a private tracker), red flags are going to start popping up. Any half-brained network administrator worth his salt will be suspicious and look to investigate. If your ISP doesn’t bust you, any antipiracy groups that happen to be monitoring the torrent will be drawn to high-speed peers.
  3. Use protocol encryption
    All the modern and major BitTorrent clients, including uTorrent, Transmission, and Vuze, support a feature called protocol encryption. Basically, the headers of any BitTorrent packets are obfuscated to disguise the nature of the traffic. Note that the actual data in the packet is not encrypted, however. Though this method is not at all foolproof, it will at least create a shadow of doubt as to the nature and purpose of that high-volume traffic going through the network.
  4. Use an IP blocklist
    As with #3, this method is nowhere near foolproof. However, it will afford you some protection in that it prevents you from connecting to known bad/malicious IP addresses that might be connected to watchdog groups/government agencies/etc. Several of the leading torrent clients support loading a blocklist in one format or anoather. If you’re using uTorrent, be sure to checkout my uTorrent IPFilter Updater, an in-house production of Binary Inspirations.
  5. Use private trackers, if possible
    Of course, this is not an option that’s feasible for everyone, including the casual user and newcomers into the BitTorrent world. Since private trackers have a limited user base, the risk of being monitored by copyright outfits is lower than on a public tracker. The smaller and more obscure the site, the less likely that any members are “double agents”. Additionally, some private sites have entry requirements and interviews that make it more difficult for malicious users to infiltrate (though not impossible - *cough* TorrentLeech *cough*!) The fast speeds and other perks of private trackers make them an option worth investigating if you haven’t already.

Friday, January 29, 2010

Z-Alarm 2 (version 2.2) released

Time for a new Z-Alarm release. Version 2.2 brings:

  • overhauled timer management and more responsive user interface
  • randomized alarm buzzer tones (you’ll never, ever get used to it)
  • Spacebar shortcut to hit the snooze button (no more stumbling around drowsily trying to move the mouse)
  • Detailed artist-title tag info display (for supported file formats)
  • More attractive-looking snooze button

More information and download:
Z-Alarm 2 (version 2.2)

mktorrent-GUI version 1.0 released

mktorrent-GUI is a Windows-based GUI frontend to the console-based (Linux/UNIX native) mktorrent tool. There don’t seem to be any decent standalone torrent file creators on Windows. There is MakeTorrent, but that was last updated in 2004 and doesn’t support more modern features like private flags. My frontend aims to address these shortcomings and expose all of the functionality of mktorrent to the user via an easy-to-use interface.

Of particular interest to hardcore torrenters is the batch mode feature. If a directory is specified as a source, mktorrent-GUI will scan one level deep for subdirectories and automatically create a torrent for each subdirectory. All of the usual features such as comments, piece size and the private flag can be set.

More information and download link:
mktorrent-GUI version 1.0

Saturday, January 16, 2010

Corsair H50: CPU cooling, redefined

Air cooling is simple and inexpensive, and for this reason it is by far the dominant method of CPU cooling. However, they aren’t flexible; overclocking will often overwhelm the cooler’s ability to regulate temperature. This was precisely the problem I ran into with my desktop rig:

  • Case: Cooler Master Centurion 5 Blue
  • PSU: Raidmax RX-530SS Hybrid 2
  • CPU: AMD Phenom X4 9850 Black Edition (125W TDP)
  • Cooling (old): Arctic Cooling Freezer 64 Pro 92mm
  • Motherboard: Foxconn A7DA-S
  • RAM: 2x2GB OCZ Reaper HPC DDR2-1066 (the good old days, when memory was dirt cheap…)
  • GPU: Sapphire Radeon 4830 512MB GDDR3
  • HDD: Western Digital Caviar Blue 640GB
  • Optical: Samsung SH-S223B
  • Add’l fans: 120mm, 2 x 80mm

At stock clocks and voltage, the CPU would idle around 33-35 degrees C. Seems pretty normal, right? Whenever the CPU encountered a heavy load, temperatures would easily skyrocket past 61C, which is AMD’s specified thermal limit for this particular chip. I was forced to take it easy with demanding applications like video encoding and processing – overclocking, of course, was completely out of the question. The latter was especially unfortunate as my chip seems to need a bit more voltage for any decent overclocking to happen.

So I decided to something about it.

After quite a bit of research, I came across the Corsair H50. It’s known as a closed-loop liquid cooler. Water/liquid cooling obviously provides vastly improved performance over air cooling, but a decent full-fledged setup with a pump and radiator is much more complicated to set up, and also much more expensive. The risks of watercooling (fluid leakage, regular maintenance) are also something to consider. The Corsair H50 claims to provide the benefits of liquid cooling in a completely sealed, compact package.

Corsair claims that installation is easy, but it ended up taking longer for me (maybe it was just a result of my own clumsiness?) I ended up doing some steps out of order before everything came together.

The H50 comes with a “high-efficiency” 1700RPM 120mm fan for its radiator. The radiator allows you to attach an additional 120mm fan to it to create a push-pull setup, which I did by using my existing case fan.

The results? Nothing short of phenomenal. Check out these temperatures:

idle: 27-29C (2.6GHz @ stock 1.28V); 33-35C (3.0GHz @ 1.312V)
load (running Prime95): 45C (2.6GHz @ stock 1.28V); 54C (3.0GHz @ 1.312V)

Under a more realistic load, my temps don’t go above 47C.

If you need serious cooling without the hassle of a full-blown enthusiast setup, I wholeheartedly recommend the Corsair H50. You’ll be blown away by what it can do.

Thursday, December 10, 2009

Spicing up Thunderbird 3 (Windows) with userChrome.css

After experiencing the raw speed of Thunderbird 3 + IMAP, I immediately ditched Windows Live Mail. Admittedly, the latter’s default interface is much easier on the eyes. But Thunderbird can be given a facelift, thanks to some userChrome.css tweaks. After some Googling, I came up with the following. This adds green-white zebra stripes to the message index and increases font sizes in the message index as well as the header and folder panes.

/* better looking fonts for folder pane and message list */
#folderTree > treechildren {font-size: 13px; font-family: Segoe UI;}
#threadTree > treechildren {font-size: 16px; font-family: Segoe UI;}

/* Light green, high-contrast zebra stripes in message list */
#threadTree treechildren::-moz-tree-row(odd) {
-moz-appearance: none !important;
background-image: none !important;
background-color:#EEFFBB !important;}

#threadTree treechildren::-moz-tree-row(odd, selected) {
background-color: Highlight !important;
}

/* increase font size in header pane */
#msgHeaderView {font-size: 14px !important; font-family: Segoe UI !important;}





Here’s a screenshot of my tweaks in action (sorry about the massive amount of blurring):





Enjoy your beautified Thunderbird!