Group items tagged

Reflective Practitioner

Reflective Practitioner.  

The reflective writing has been valuable but definitely the nearly 4,000 comments have been even more of a learning experience. This is the single best professional development experience I've had.

What do you think are the most important features a social network should have? How would you prioritize them? Do you plan to Build Less or go big? If building less, what is the minimal set of features you can get away with? We plan to “build less.” These are the features which we aim to complete first: 1. A good secure protocol, encrypted at every leg, including a specification for a lightweight, probably HTTPS, RESTful set of routes. We see all of this communication happening between two Diaspora servers, rather than strictly between peers. We realize there is the problem with polling with this model, but we think there are several tricks worth trying which all have their relative pros and cons: PubSub (fast and easy, requires some level of centralization), querying friends servers from the browser side and posting responses back (requires browser side decryption) to name a couple. Alternatively, we are considering going with XMPP altogether due to the ability to be able to push content between nodes, but we need to research it further to see if it is something we would want to implement. 2. A datastore and corresponding interface that can store all of your stuff in one place. MongoDB is what we are looking at for V1, but the redundancy of TahoeFS is intriguing(as well as serving a slightly different purpose). 3. A clear extension framework. Diaspora will be service-agnostic and we will need to make it easy to import from and export to any format/web service. It is also our goal to make Diaspora as content-agnostic as possible, by providing abstract data types and an easily extended UI so that whatever new content people want to store and share can be integrated without re-rewriting parts of the whole application stack. 4. Be your own OpenID provider. Having a single identity across lots of services is great, but why trust a web service to hold it? Once we are the keepers of our own data, we can also selectively allow services access to it through Oauth.

Almost every adult I’ve talked with in these countries shares a belief that the path to success is paved with science and engineering.

scientists and engineers are celebrities in most countries

Already, 70% of engineers with PhD’s who graduate from U.S. universities are foreign-born. Increasingly, these talented individuals are not staying in the U.S – instead, they’re returning home, where they find greater opportunities.

The standard model for asynchronous conversations is discussion forum software like vBulletin.  I've talked before about the significant value that can be obtained as part of Discussion Forums for Knowledge Sharing at Capital City Bank and how that translates in a Success Formula for Discussion Forums in Financial Services.  I also looked at Making Intranet Discussion Groups Effective.

However, I've struggled with the problem of destinations vs. social networks and the spread of conversation (see Forums vs. Social Networks). 

Talkwheel  is made to handle real-time group conversations and asynchronous ones.  It can act as an instant messaging service a bit like Yammer, HipChat for companies and other groups, but the layout is designed to make these discussions easier to see, archive, and work asynchronously.