(HBSN) How to Build a Social Network

something to keep in mind when the user-interface is developed.

I think they are referring more to the kind of question. A query like "who is the oldest living American president?" is best suited for a Library paradigm, whereas a question like "is the current president of the US doing a good job in repairing the economy?" is really more of a village paradigm. I most likely will 'trust' the library answer on the first one, but will probably become en-snarled in endless debate with my Village on the second. The point is I think, that more and more, people are asking questions that the traditional library of knowledge cannot effectively answer, even with functional semantics in place. Long live The Village. Now, who IS Number 6?

perhaps we should be checking out Cargo

Separate group to discuss translation features

someone beat you to it Kurt.

to what, exactly? back to my gardening... don't worry about the vase. cookie?

there is no spoon.

"On Karma: Top-line Lessons on User Reputation Design In Building Web Reputation Systems, we appropriate the term karma to mean a user reputation in an online service. As you might expect, karma is discussed heavily throughout the more than 300 pages. During the final editing process, it became clear that a simple summary of the main points would be helpful to those looking for guidance. It seemed that our first post in over a month (congratulations on the new delivery, Bryce!) should be something big and useful... This post covers the following top-line points about designing karma systems, drawn from our book and other blog posts: * Karma is user reputation within a context * Karma is useful for building trust between users, and between a user and the site * Karma can be an incentive for participation and contributions * Karma is contextual and has limited utility globally. [A chessmaster is not a good eBay Seller] * Karma comes in several flavors - Participation, Quality and Robust (combined) * Karma should be complex and the result of indirect evaluations, and the formulation is often opaque * Personal karma is displayed only to the owner, and is good for measuring progress * Corporate karma is used by the site operator to find the very best and very worst users * Public karma is displayed to other users, which is what makes it the hardest to get right * Public karma should be used sparingly - it is hard to understand, isn't expected, and is easily confused with content ratings * Negative public karma should be avoided all together. In karma-math -1 is not the same magnitude as +1, and information loss is too expensive. * Public karma often encourages competitive behavior in users, which may not be compatible with their motivations. This is most easily seen with leaderboards, but can happen any time karma scores are prominently displayed. [i.e.: Twitter follower count] "

Remember these? Ha Ha However, we could use this to keep track of all of our stuff in Diigo and elsewhere.

That's pretty cool. I like how the connection chain is dynamic as you click it. Lots of wasted real estate at the bottom however. It would be nice to get a preview of the selection instead of just a link. Man you connected a lot of stuff!!!

This was a real early version. I'm working on a version with everything that I've done in Twine using this app that has more than 27k items to it. It's the one that Bent help me make a file with NSA. I'd really like to know if Twine will maintain the urls from T1 after going to T2. If I could get the Twine files into Diigo, I could do a bulk change, and recast the front end.

while this is not a social network, MUCH to learn from here, architecturally, conceptually

Great video; substantially, however, much as we are thinking about using APIs from the various groups we're a part of in the socnet areas (we like this, but don't like that, this is useful, forget this, et al.) This is remarkable stuff! I'm on the SIRI beta list - maybe by June they'll release the beta.

There ain't no such thing as a free lunch... OK Kurt, I built the darn group for exploring routes to a little revenue for our ragtag band of digital outlaws....

looks like the big G is getting serious...

Yep, and I see it as more exciting than threatening.

Here's the discussion on Friendfeed: http://friendfeed.com/paul/d0c8861e/google-to-add-social-features-gmail

clearly others are thinking about this in their domain, note the reference to ownership and posting references rather than content to the service (invisible to the user), taking things into one's personal stream (entanglement) and social graph based filtering

or solve the more general problem and let people manage multiple identites and authorizations / grouping metadata sets

About Adobe: They are lazy, Jobs says. They have all this potential to do interesting things but they just refuse to do it. They don't do anything with the approaches that Apple is taking, like Carbon. Apple does not support Flash because it is so buggy, he says. Whenever a Mac crashes more often than not it's because of Flash. No one will be using Flash, he says. The world is moving to HTML5.