Wade Simmons's dashboard

Wade Simmons set one of Wade Simmons' replies as an official response to "How come my Brightkite Avatar is blank?" in Socialthing

Wade Simmons replied on January 08, 2009 20:31 to the question "How come my Brightkite Avatar is blank?" in Socialthing:

Brightkite icons should now be fixed, you can force a refresh by removing and re-adding the service.

Wade Simmons set one of Wade Simmons' replies as an official response to "Facebook doesn't doesn't load, and I always have to reauthenticate." in Socialthing

Wade Simmons replied on January 08, 2009 20:30 to the problem "Facebook doesn't doesn't load, and I always have to reauthenticate." in Socialthing:

We have switched over to the new Facebook Connect method of authentication. Please try removing and readding your Facebook account (you must have popups enabled for socialthing.com). Let us know about any issues you encounter.

Wade Simmons set one of Wade Simmons' replies as an official response to "lifestream error on home tab" in Socialthing

Wade Simmons replied on January 08, 2009 20:27 to the problem "lifestream error on home tab" in Socialthing:

I think we have this fixed, can you try again and let me know if you are still having problems?

Wade Simmons set one of Wade Simmons' replies as an official response to "lifestream error on home tab" in Socialthing

Wade Simmons replied on January 07, 2009 16:53 to the problem "lifestream error on home tab" in Socialthing:

I can see what the problem is, and I am working on fixing it. I'll keep you updated.

Wade Simmons set one of Wade Simmons' replies as an official response to "lifestream: There was an error processing your request" in Socialthing

Wade Simmons replied on December 30, 2008 18:21 to the question "lifestream: There was an error processing your request" in Socialthing:

The issue should be fixed; your lifestream should be working again now.

Wade Simmons set one of Wade Simmons' replies as an official response to "lifestream: There was an error processing your request" in Socialthing

Wade Simmons replied on December 30, 2008 17:55 to the question "lifestream: There was an error processing your request" in Socialthing:

I can see what the issue is, and I am working on a fix. I will keep you updated.

A comment on the question "login bug won't let me sign up." in Socialthing:

ollie_lufc: if your issue is with facebook.com, please investigate it here: http://www.facebook.com/help.php?ref=pf . This is the support forum for socialthing.com – Wade Simmons, on December 22, 2008 17:59

Wade Simmons set one of Wade Simmons' replies as an official response to "SocialThing seems to be down." in Socialthing

Wade Simmons replied on December 13, 2008 07:45 to the problem "SocialThing seems to be down." in Socialthing:

We experienced some downtime tonight due to some hardware issues. The site is back up, but may be slow until the caches can warm back up.

Wade Simmons set one of Wade Simmons' replies as an official response to "Some Facebook friends' updates are missing" in Socialthing

Wade Simmons replied on December 09, 2008 17:26 to the problem "Some Facebook friends' updates are missing" in Socialthing:

On Facebook, a user can select that they don't want to share information with applications that they don't have installed. Your friends must have enabled this privacy feature; there is nothing that we can do about it.

Wade Simmons replied on December 03, 2008 22:46 to the problem "Crashing..." in Socialthing:

Can you try removing Twitter from your account and re-adding it? May need to give it a few minutes after you do this for it to catch up.

Wade Simmons set one of Wade Simmons' replies as an official response to "Links in tweets redirecting to a concatenated socialthing.com address" in Socialthing

Wade Simmons replied on November 26, 2008 23:28 to the problem "Links in tweets redirecting to a concatenated socialthing.com address" in Socialthing:

I have a fix for this ready, but we probably won't be able to deploy it until after the Thanksgiving holiday. Only links without the "http://" are affected.