You can find a live instance of the framework running on the Michigan Ruby Community site at:
http://www.rubymi.org

After doing the research with finally decided to use facebook connect in the specific project we were doing the research for. You can read my other posts about it.

Each project is independant and has it’s own particular solution I think. Using facebook connect has been really great so far, and a very important thing is that normal users are begging to use it. For implementing a complete social network so far we never used a complete framework, we just install the plugins we need and develop (or reuse code we already have) what’s needed.

From my point of view I think an average advanced developer will prefer to develop the site himself installing the plugins he wants, using the authentification he wants, and so on.

For a begginer develper it may be kind of hard to modify plugins that are dependant whithin each other. What I’m trying to say is that I think tog should be oriented to begginer developers developing a social network.

Anyway, I think it’s a really awesome project

As commented here, there is a balance to maintain between modularity and the “work-out-box” experience and this can do sometimes the dependencies between plugins stronger o weaker.

We’ve try as much as possible to put this balance in the developers shoulders, allowing them to modify the behavior in the fashion they prefers…

Taking this in to account, and even if I accept that could still be some weird dependencies in tog, I think it’s still easier to install/remove/overwrite small pieces of code like plugins (or even develop the one you need) that take the “everything-inc.” approach other platform take and get the useless parts out.

This is shaped by our vision of the social networks as different communities with different needs and the lack of a magic potion with “all the features ever needed by a social network”.