Blog Posts

September 2008 - February 2009

libpurple-facebook package soon

Posted by Justin Haygood on Tuesday, February 10, 2009;

I'm considering releasing my libpurple-facebook package in tar.bz2 form so that people using any Linux (or *nix with Pidgin/libpurple/GTK) distro can install. It's basically pidgin-facebook chat with a modified build system that makes sense (read: it uses autoconf).  Look out for it!


Vacation

Posted by Justin Haygood on Wednesday, January 7, 2009;

I'm having a lovely vacation, spending time with the love of my life, Shelley


libpurple-facebook updated in OBS

Posted by Justin Haygood on Monday, December 29, 2008;

I have updated libpurple-facebook (openSUSE 11.0, 11.1, Factory package for pidgin-facebookchat) to 1.46, which includes a fix to make it load in openSUSE's default Pidgin.


  • openSUSE 11.1: http://download.opensuse.org/repositories/home://jhaygood/openSUSE_11.1

  • openSUSE 11.0: http://download.opensuse.org/repositories/home://jhaygood/openSUSE_11.0

  • openSUSE Factory: http://download.opensuse.org/repositories/home://jhaygood/openSUSE_Factory



Use Facebook IM from Pidgin

Posted by Justin Haygood on Saturday, December 27, 2008;

There's a much better way to do this now. See my updated post here
I just packaged the pidgin-facebookchat plugin for openSUSE 11.0 and openSUSE 11.1 in my home project in the openSUSE Build Service. The package is called libpurple-facebook to be consistent with other packages.
Enjoy, and please let me know if there are any problems!


Announcing: Geeko Gears

Posted by Justin Haygood on Monday, December 22, 2008;

What is Geeko Gears? Simple: its a project to redo the build system of Google's open source Gears software.
Initial Goals:


  1. Use autotools to create the Makefile

  2. Link to system libraries instead of using internal ones

  3. Allow to be built for all platforms openSUSE supports (32-bit, 64-bit, PowerPC)

  4. Remain 100% API compatible with upstream



Some misconceptions about display advertising....

Posted by Justin Haygood on Saturday, November 22, 2008;

A lot of people I know have some common misconceptions about display advertising online. Here's a few myths about display advertising:
So what if I block ads? Not like I click on them anyway.... Except for Google Ads and a few others, most advertisers pay using a "CPM" model. They pay so much money per 1,000 impressions. So even if you don't click on the ad, the website makes money.
But ads use up so much bandwidth, etc... You must not have ever dealt with site specs? Most web publishers (websites) are very anal retentive about their 30 KB file size limit. Your ad is 30.1 KB? To damn bad.
Ads track me uniquely. Now some companies do this, but not all of them. I work for one of the largest rich media companies in terms of traffic (EyeWonder), and I can tell you, we don't track users uniquely. We do however aggregate alot of information about what users do with the ad, but its aggregated and each logfile is deleted immediately after processing.


I voted!

Posted by Justin Haygood on Tuesday, November 4, 2008;

I have my "Georgia Peach". For people not from Georgia, that means I got the little sticker with a Georgia peach on it that says "I'm a Georgia voter". BTW, I voted Libertarian, except for when there wasn't one, then I voted Republican.


Going to Adobe MAX...

Posted by Justin Haygood on Tuesday, October 21, 2008;

I will be at Adobe MAX from November 16th to November 20th. If you want to meet up with me in San Fransico, please let me know!


Proposed High Resolution Timer API

Posted by Justin Haygood on Wednesday, October 1, 2008;

Long time since I've posted on Planet WebKit:
Here's a proposed high resolution Timer API for WebKit (and hopefully HTML5). It's based off of Adobe's "flash.utils.Timer" API found in ActionScript 3.0.
Timer : EventDispatcher
Properties:


  • currentCount:Number => Total number of times the timer has fired since it started (at 0)

  •  delay:Number => The time, measured in millisecondsseconds, between timer firings. Precision is browser defined, but should be at least 1ms

  • repeatCount:Number => The total number of times the counter is set to run. If the timer is "0", the timer will run forever or until its stopped.

  • running:Boolean => If the timer is running or not


Methods:



  • start() => Starts the timer if the timer is not running

  • stop() => Stops the timer if the timer is running.

  • reset() => Stops the timer if its running, and resets "currentCount" back to 0.




The timer will implement the browser native event dispatching system (W3C for most, IE proprietary for MSIE), and will fire the following events:



  • timer => Dispatched whenever the timer reaches the interval specified by the "delay" property.

  • timerComplete => Dispatched when the timer's repeatCount reaches 0.


Please note the timer will be a high resolution timer, with no minimum bound, so there's no compatibility issues when using setTimeout/setInterval. Plus, the API is simple enough to be implemented in terms of setTimeout/setInterval on browsers that do not implement the proposed.


Please leave feedback on the proposed API.


Some notes:



  • Changes from flash.utils.Timer: delay is measured in seconds instead of milliseconds, since its defined to be a JavaScript number, which has the precision equivalent to a "double" on a standard Intel x86 system.

  • Repeat Count defaults to 0, meaning, go on forever. If you want it to be "one shot", then set repeat count to 1.


Example Code:

var timer = new Timer();

timer.delay = 0.01;

timer.repeatCount = 1;


// Add Event Listeners

if(timer.addEventListener) timer.addEventListener("timercomplete", OnTimerComplete); // W3C

else if (timer.attachEvent) timer.attachEvent("ontimercomplete",OnTimerComplete); // MSIE


// Event Lsitener

function OnTimerComplete(e)

{

if(!e) e = window.event; // MSIE


// Do Something

}




AT&T FastAccess POP3/SMTP Servers

Posted by Justin Haygood on Thursday, September 25, 2008;

AT&T FastAccess DSL users might be used to using "mail.bellsouth.net" as their POP3/SMTP servers for a long time now. However, AT&T recently introduced 2 new servers that are (1) Secure (via SSL), and (2) work when not on the AT&T network.
POP3: fpostoffice.isp.att.net, SSL Enabled, Port 995
SMTP: fmailhost.isp.att.net, SSL Enabled, Port 465
If anyone wants instructions for their particular mail client, reply back to here, and I'll send you instructions (as well as provide them on here).


← Newer Posts Older Posts →