changcommaalex

Don't want investors in my next company to ask why one of my cofounders gets to designate himself the founder while I'm labeling myself a cofounder.

I'm starting to incubate my next company and don't want to have to explain to investors why one of my cofounders is calling himself a founder when I'm still labeling myself a cofounder. Additionally, he's phrasing his work profile/resumes etc to indicate that he was the originator for the idea of the company.

Yes this is the case. He's now claiming that he was the originator for the idea which is far from the truth.

It's generating the errors because it's not detecting a parent container (cross domain iframe communication).

Facebook doesn't want people to enable cross domain authentications/spoofing. If Facebook enabled their plugins to work inside iframes external to the Facebook environment, it'd be easy to maliciously authenticate users to give data to a fourth party.

This is working as designed. The author of the article didn't fully investigate why he was getting users with the fragment and if he alters his code, will negatively affect page performance on his page.

In order to do cross domain communication, Facebook iframes the current page with the fragment. When Facebook's javascript library in the iframe detects the parameter, it blanks the page to reduce the render time that it takes for the iframe to complete so that it can generate the cross domain communication channel faster.

Originally, Facebook had developers upload a file to act as the cross domain script but became a problem for some people who couldn't do this so for the most part. This is still doable, but most people don't read the documentation clearly and Facebook doesn't want to complicate it's message of a simple install( http://developers.facebook.com/docs/reference/javascript/FB.... ).

What is worse is that the user id's of the poster of the photos is encoded into the image urls which makes it extremely easy to identify the owner.