Group items tagged

"Ambient overload doesn't involve needles in haystacks. It involves haystack-sized piles of needles. We experience ambient overload when we're surrounded by so much information that is of immediate interest to us that we feel overwhelmed by the neverending pressure of trying to keep up with it all. "

"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] "

FishMan - this sounds a little bit like Ning, a socnet for all folks (build your own!) Why do you think there is no monetization by any one of these efforts? That's a key part to what I'm imagining for HBSN. Hmmmmm

Checking into ad.ly, their pay rate and advertisers aren't based on your attention, they are based strictly on the number of followers you have. Their whole model is wrapped around slight-of-hand diversion. They figure that by dropping an ad tweet into your own personal twitterstream on an every other day basis, will appear innocent enough on the surface, that some (>1%?) will mistake it for something you personally tweeted and since they follow you blindly like hooded lemurs in Jonestown, they;ll drink your koolaid and make a buying decision. Seems a bit underhanded to me. And they aren't paying me because I might be a good target, they are paying me because I have a high enough unwashed masses quotient to justify the exposure. I set my rate for $5000 figuring that even though I have fewer than 100 followers, they are quality followers and not bots (except for Kurt) and that my endorsement to them is worth a great deal. So far, the till's empty.

if you advertise to me I will recycle it on an hourly loop and feed it back to you

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?

excellent article on how to build the next generation of infrastructure and what some key themes are.

round up of socnet approaches, courtesy link by michael j p

Very nice. Now this is done by the FSF (Free software foundation) and all projects listed here are freeware (as opposed to both open-source and commercial ware). The group behind it (http://groups.fsf.org/wiki/Group:GNU_Social) has nice goals: "GNU social, true to the Unix-philosophy of small programs to do a small job, will be a decentralized social network that you can install on your own server. What if you could authorize your server to reveal as much, or as little information about you to other sites, as you wish... one time, one day, or forever?" "But you'll never beat Facebook, so why bother? Maybe everyone in the world won't use this, but not everyone uses Facebook either. Privacy is important, and lots of people value their privacy as well as their freedom to ensure the software they're using isn't doing things they don't want." "It is still in open discussion on the mailing list, if it makes sense to have this technology server-based or rather, for reasons of privacy, based on the user's computer. The current consensus seems to be, that there is a need for something quick that will federate existing server-based social community servers, yet at the same time we should maintain a long-term look on how to provide peer-to-peer privacy." See also: http://groups.fsf.org/wiki/Group:GNU_Social/Ideas

perhaps we should look back at this?

I do not see the point in moving to ning, less capable than diigo

Never liked making money very much - too much trouble - I'm a retired professor, for God's sake! But, I love working with people that get in my head and stay there (a paraphrase of one of your remarks, I believe!) And, I like doing good things ...

This is an example of how NOT to build a social network. I did a search for 'twine' on this page, and couldn't find one example of it - but, all of his tweets are surfaced in a column on the right. Oppsss.

In Mac OS X, control-command-D. Let the world be literate!

@François - +1 on "Voodoo and all mysticisms, but things change fast nowadays" - They are changing fast, and we can look forward to these things changing faster than ever now and into the future!

Ya'll come and give us your opinion.

Agree with Frank. There is no use in letting Barney tell us where he lives, if we want to use the map gadget to choose a good place for a meatspace meeting. So this particular wave, given its intent, should have been restricted to the group. In many cases, I think it could be harmless to open a wave to the public: the crowd can contribute good things, we all know that... But I still think that, by default, wave access should be restricted to group members. It would maximize the sharing of relatively private or "sensitive" information within the group. It would also help keeping the discussions on topic (side-tracking is very easy in all forum discussions and the more people you have in the conversation the more side-tracking you get). Now of course anyone in the group can invite anyone, even "Public" into the wave: just like anyone who has access to a private document can copy it and paste it on a blog or any public place.

Yes F1 (Francois, I will be F2)!! i think we can use the wave structures to keep things private and the fact that any of us can add anyone can be moderated by convention and the trust we have begun to build with each other. plus the reinforcement from the system, in that we all can see who has added whom. Plus the ability to delete participants will come along eventually. Thanks F1!!!

Compare: "MySpace User Data For Sale - Information being sold to third parties includes blog posts, photos, status updates, and more." http://www.pcworld.com/article/191716/myspace_selling_user_data.html Looks a bit scary, doesn't it? Is P2P the solution?

yes, but if it's a central site, it's not peer to peer. peer to peer requires a "desktop" solution. ironically, peerson is blocked at libraries, so it makes it useless. a program that can fit on a thumb drive cannot be blocked like this. *web services* - not *web sites* are the key.

Ha Ha

Of course is should be how to destroy a social network. But, I'm still interested what Evri will do with it, and, since so much of our input is still on Twine, it seems like it should be worth looking at what, if any, the improvements could be. What do you think? Are you going to keep an eye on the progress? I like the EvriVerse By EvriView, which I use on my iPhone. It's clever, and has link-types around tags that lead to some interested 'faceted' search. So, ... maybe there will be some interesting outcomes from this relationshiip.

You can't destroy the network, but you can destroy the network service. The map isn't the terrain. Only the most sociopathic individuals have the power to destroy the actual network, and since a network is generally self-healing (but still subject to scarring), chances are the only they'll do is sever their link to the overall network. It's the Triumph of the Subjective.