Quick Contact

Syndication

Sponsors

Administration


Posted on February 11, 2010 at 11:07 am - by Corey DeGrandchamp

Pidgin Facebook Chat Setup & Log Transfer

Pidgin Logo

Yesterday, Facebook announced that Facebook Chat now fully supports the XMPP protocol.

This is great news, because we can now all ditch whatever hacked-together methods we were all using to connect to the Facebook Chat service with Pidgin, if you were ever using one. I’ll also cover how to transfer your logs over from the old connection method to the official connection method below.

CLIENT SETUP

1. You’ll first need to go to your Accounts menu, then to Manage Accounts, then choose Add…

2. From here, you need the following settings:

  • Protocol: XMPP
  • Username: {Your Facebook username, not your email address, to get this you should be able to go to your Facebook homepage, and hover over your “View My Profile” link, it will be http://www.facebook.com/username and you’ll need the username part, and that is all.}
  • Domain: chat.facebook.com
  • Password: {Your Facebook password}

3. Switch to the Advanced tab, and uncheck “Require SSL/TLS” and check “Allow plaintext auth over unencrypted streams”

4. That’s it, if you were using an old method to connect to Facebook, be sure to remove that account!

LOG TRANSFER

In your Pidgin log directory, usually located at:
%APPDATA%Roaming.purplelogs (Vista/7)
-OR-
%APPDATA%.purplelogs (XP)
unless you set up PURPLEHOME environmental variable (like I did), but if you did this, you should know where they reside… and as for Linux users, you should also know where your log directory is already…

You’ll see some folders in there, with various logs for accounts.
You will have a folder called “facebook” with a “username” directory inside it, and now a new one called “jabber” with a “username@chat.facebook.com” directory inside of it.

In order to transfer the logs, you need to rename all the folders in your “logs/facebook/username” directory from

######
to
u######@chat.facebook.com

and then move them to the “logs/jabber/username@chat.facebook.com” directory.

All your logs should continue to work properly after this.







Posted on January 8, 2010 at 1:30 pm - by Corey DeGrandchamp

Call of Duty: Modern Warfare 2 – Titles & Emblems Checklist

CURRENT VERSION

0.5

I’ve noticed a few sites have full lists of titles and emblems for Modern Warfare 2 players to look at. However, no site had any form of EITHER an electronic checklist, or a printable checklist…

I’ve taken the liberty to create my own with the data from those websites. Take a look at the preview below.

Checklist Preview

Checklist Preview

Currently I have only completed the Titles, the emblems are coming in a few days time.
Anybody who uses this who doesn’t have a clantag set yet, feel free to use [JAWA].

DOWNLOAD LINKS BELOW!

Titles & Emblems Checklist – Excel 2007 (Or Newer)

Titles & Emblems Checklist – Excel 2003 (Or Older)

Titles & Emblems Checklist – PDF (Temporarily on Scribd for now, until v1.0)







Posted on December 16, 2009 at 11:30 am - by Corey DeGrandchamp

Realizing MacBook’s Impending Doom

It’s been quite a few years since I’ve purchased my MacBook.

MacBook 1,1
Model Version 1, Revision 1.

It’s been though hell and back, with a power adapter that lit on fire, a battery going dead, and a (still un-fixed) dead SuperDrive.

I recently realized that I also have the infamous failing hard drive that was shipped in some, but not all, first revision MacBooks. Yay for me!

This has been a known problem since a few weeks after the MacBooks were released, yet Apple still hasn’t issues any sort of official statement, or recall of its failing products.

I was lucky enough to get my power adapter and battery replaced, but that is only because they likely wanted to avoid any legal issues with A CABLE SMOKING AND SPARKING, CAUSING A FIRE IN A COLLEGE CLASSROOM!

I’ve been lucky enough to not have any major problems with this HDD yet, but I now know it’s only a matter of time before it grinds a hole through its top layer of the platter.