Please login or register to participate.

Cynapse scheduled downtime - Today, November 16, 2010, starting 10:30pm GMT

— Posted by Romasha Roy Choudhury


We have scheduled a short downtime for server maintenance, today, November 16 from 1030PM GMT to November 17, 7AM GMT. We plan on being down for approximately 8.5 hour

During this period, the following sites will be unavailable:

  • Cynapse Community
  • Cynapse Blog
  • Cynapse Customer Care Portal
  • - new site creation and payments will be closed. You can continue to use your Pro sites or access free notes that you might have created.

We apologize for any inconvenience this brief outage may cause. We'll be back soon!

Thank you for your understanding. If you have any questions, please feel free to comment here, connect with your account executive or directly get in touch at info at cynapse dot com.

Last workflowed by romasha
Nov 16, 2010 01:59 PM

SUGGESTION: Make activity streams interwork with Tweetdeck and users on other networks through support for "OStatus"

— Posted by Anthony Leonard

Many people now keep in touch with their social networks (Twitter/Facebook/Buzz/etc) using mobile or desktop "third-party" client apps like Tweetdeck/Seesmic/Twitdroid/Tweetie/Flipboard etc. These apps make use of disparate APIs from all these services, and focus on making it easy and fun to monitor them all simultaneously, and cross-post where appropriate. The UI experience of these apps goes well beyond anything that the actual social network providers (Facebook/Twitter etc) can support in their "silo'd" native interfaces.

Recently attempts to create open-source versions of such social networking systems (StatusNet, Wordpress, etc) have begun coalescing on OStatus as a standard API for public updates and comments that third party client apps could interwork with, with the promise of two-way management of secured updates and comments to come. Even better, OStatus handles interworking across such systems, using federated (Webfinger) IDs. This means that, eventually, someone logged into their university's own Wordpress system could comment on someone else's post on another university's system - all using the great UI supported by their favourite third party client app.

In theory, if supported OStatus it could also join this club. This gives users the opportunity to use in the same way that they're already consuming their social web, and could open interactions to a legion of other users who are not even registered within initially, but who are trackable through their Webfinger IDs. BTW Webfinger is currently supported by Google (all "" addresses) and Yahoo (apparently). This fits the university model very well, where researchers commonly need to discuss across institutional boundaries.

I accept that this is very hard request to fulfill. OStatus is not yet mature, and is a collection of underlying components that are also not yet mature. However the benefits of keeping track of updates from your own organisation's system alongside the rest of your life (Twitter, FB, etc), and interworking with other networks, would increase usage and usefulness dramatically. For these reasons I think that support for OStatus and/or its components should be considered as part of the long-term direction for

Some OStatus references:

Last discussed by dhiraj
Aug 24, 2010 12:32 AM
Last edited by viraf
May 19, 2010 11:53 AM
Last edited by viraf
May 19, 2010 11:56 AM
Last discussed by offray
May 21, 2010 01:27 PM