I’ve had difficulty quarantining the feature-itis, because I can’t stop dreaming about integrating Twitter and Facebook differently.

What I envisioned in these dreams (which I hope you won’t call nightmares) is something I’m calling an ‘integration aspect’ which would display the contents a Twitter account, Facebook wall, etc. This would be different from the way it is now: limited to a single Facebook wall or a single Twitter account only accessible as write-only when posting to the world. I think it would be useful to read and write to ‘integration aspects’ which are Twitter accounts, Facebook Walls and Facebook Page Walls, and whatever API hackers deem hackable in their integration adventures. ‘Integration aspects’ would become part of the ‘all aspects’ aggregation and who knows, maybe even serve as a way to drag and drop share invitations from Diasporans to Twitter and Facebook, et. al.

You might be asking yourself, “Why do we need to support multiple Twitter accounts?” Perhaps we don’t NEED it, but many people have at least two accounts, especially for business purposes. In some ways, these multiple accounts are their attempt at ‘aspects’ in the world of Twitter.

You might be asking yourself “Why do we need to support more than one Facebook wall?” Facebook pages have their own walls which are manageable under one account.

The presence of SaaS dashboards which already integrate these social network features… and the fact that some of them charge $5 to $15 per month per user… perhaps indicate demand.

You might be asking yourself “How on earth and in Diaspora would we execute these features without causing API drama?” That’s a good question. We would most likely need to heavily cache the results from querying these social networks at large. It’s doable and others have done this with their integration platforms.

The value proposition is that these features would create a multi-threaded integration environment which is consistent with the aspect-driven, contextually-aware user experience we have already instigated.

- Asher Bond
asherbond@joindiaspora.com
https://convore.com/diaspora/ui-ux-uask/

Finally a social media dashboard that integrates your LinkedIn, Facebook, Twitter, Myspace, Tumblr, and other social networks et. al. into one mobile-friendly platform that let’s you sign on once and manage many social media campaigns and social media teams. Multi-tenant and multi-platform? Yeah.

Today Hootsuite announced that you should refer your friends. If you might be an evangelist, here’s how you can become an affiliate.

Social Media Analytics in Hootsuite

HootSuite Social Analytics from HootSuite on Vimeo.

(Music: Salteens / Grey Eyes – Everything They Know About Us)

Although PHP is considered to be a scripting language, PHP’s parser does in fact compile code before it is processed by the Zend Engine. Opcode caching allows compiled PHP code to be shared and recycled in memory, rather than compiling the PHP source on the fly. Opcode caching is already available in Zend Server’s community edition and will be available when PHP6 is released.

HipHop takes a much more aggressive approach to performance optimization by translating the source code into C++ which can be compiled into more machine specific instructions. Not only does HipHop compile the source code into a more system friendly language, it also rewrites your code to be more efficient. Through static binding, scripty system calls and functions such as eval() are eliminated and loosely defined types are tightened up to meet specific runtime requirements. Here is an illustration of how HipHop optimizes PHP:

According to Facebook’s Senior Engineer Haiping Zhao, HipHop reduced Facebook’s CPU overhead by 50%!

HipHop will be released tonight under the open PHP license.