Following my latest thoughts on the scheduled sharing and optimized Twit delivery, I decided to conduct a little experiment.
This is how FavHub was born.
So, what is favhub? It is a nifty application hosted in the cloud that aggregates the online resources I like and reposts them for a broader audience. It’s limited for the moment to the Tweets I favor and articles I share or like in Google Reader and my bookmarks in Delicious.The nifty thing about it is that it will always RT. As awkward as this may sound, I fancy the idea that credit should be given where necessary.
Here comes the geek-ish part: for tweets it’s always easy to track the source as the application is aware about the user that originally tweeted, but what happens with articles in Google Reader or bookmarks? It’s pretty easy: Using ContextVoice (the API powering UberVu ) I am able to track the very first reaction on Twitter related to the particular URL I’m sharing. 
All the backend processing is beautifully powered by YQL so there’s minimum processing I’m doing on the server side.
Now with these nice tricks rolling, I’m making favhub public and waiting for reactions or comments to the product.
As a final disclaimer, I still keep my thoughts that this type of behavior is somehow destroying the social value, but the experiment is just a follow-up to the comments I received. The main goal of this is to try to discover the potential value inside this kind of sharing.
