+FeedManager.php:  Fixed null variable exception when no feeds have been fed
Small fixes to the new Wunderground plugin
Fix to Wunderground plugin for locations that contain spaces
Bumping copyright year
Fixing urlencoding bug
Spaces in location should always function as expected
Merge branch 'master' of https://github.com/phergie/phergie
Modified Phergie_Plugin_Abstract->findDataFile() to check for a local path first (versus a PEAR path) to work around an error in unit tests involving PEAR_Config assigning a new object instance by reference, which is deprecated
+Twitter OAuth Tweeting

Implementation of Tweeting through OAuth.

Configuration
------------

It is required that the user create an application with both read and
write access through Twitter Developer API and authenticate their
account for said application.  This information should then be stored
within the config file loaded with Phergie.

It is possible to hide a consumerkey and consumersecret, but I believe
that most users will have no problem with the current limitation.  Once
more basic functionality has been address, it should be modified so that
users have the option of using their own application, or one provided by
default.

* twitter.consumerkey
* twitter.consumersecret
* twitter.usertoken
* twitter.usersecret

Application
----------

PEAR module/extension OAuth is now required.  I am looking for advice as
to how you would prefer this requirement included.  I feel as though
requiring it when the user has not provided authentication credentials
would not be the best idea.  What would be the best way of making OAuth
a requirement only when specific configuration variables have values?

A new function onCommandTweet(); has been added so that users can !tweet
TWEET MESSAGE and send a tweet.  The user is notified on error, or given
the tweet back from Phergie.

Notes
-----

The four oauth credentials are private variables, but the oauth object
itself is public.  Since the oauth object belongs to $twitter, which is
private, this should not cause any problems with other plugins accessing
the data.

My experience with OOP is very limited.  Please note this when reviewing
the code.  I welcome any criticism and explanation for any of the
methods I used that you may have done differently.

I also fixed an issue where Twitter URLs were not being parsed correctly
for their ids.  Phergie will now respond with the tweet message of a
twitter URL linked within the chat.
+Twitter OAuth Tweeting

Implementation of Tweeting through OAuth.

Configuration
------------

It is required that the user create an application with both read and
write access through Twitter Developer API and authenticate their
account for said application.  This information should then be stored
within the config file loaded with Phergie.

It is possible to hide a consumerkey and consumersecret, but I believe
that most users will have no problem with the current limitation.  Once
more basic functionality has been address, it should be modified so that
users have the option of using their own application, or one provided by
default.

* twitter.consumerkey
* twitter.consumersecret
* twitter.usertoken
* twitter.usersecret

Application
----------

PEAR module/extension OAuth is now required.  I am looking for advice as
to how you would prefer this requirement included.  I feel as though
requiring it when the user has not provided authentication credentials
would not be the best idea.  What would be the best way of making OAuth
a requirement only when specific configuration variables have values?

A new function onCommandTweet(); has been added so that users can !tweet
TWEET MESSAGE and send a tweet.  The user is notified on error, or given
the tweet back from Phergie.

Notes
-----

The four oauth credentials are private variables, but the oauth object
itself is public.  Since the oauth object belongs to $twitter, which is
private, this should not cause any problems with other plugins accessing
the data.

My experience with OOP is very limited.  Please note this when reviewing
the code.  I welcome any criticism and explanation for any of the
methods I used that you may have done differently.

I also fixed an issue where Twitter URLs were not being parsed correctly
for their ids.  Phergie will now respond with the tweet message of a
twitter URL linked within the chat.
Fixed an issue where an object was being called incorrectly.
Added fix for issue #211. Plugin Remind: The bot can't be the recipient. (This time I hopefully did it in a separate branch. :-/)
Fixed a warning (undefined index) in plugin FeedTicker.
Updated db.php of plugin Tld. Most likely iana.org's source code changed as db.php parsed rubbish before.
Added plugin PingPong.
Plugin PingPong has content now.
Fixed warnings in plugin FeedParser (undefined index, accessing property on non-object).
Fixed another 'undefined index'.
Adding a block for command.prefix to Settings.php.dist
Modified the streams driver to support context options, added a related setting to force use of IPv4 to the sample configuration file
Merge branch 'master' of github.com:phergie/phergie