This is a very delicate feature — and one that we should wait on to see how Twitter moves forward with this — if only to better understand the ramifications and reactions from the community when they switch their API. My thoughts, greatly influenced by my work on the activity streams spec ( http://activitystrea.ms):
* *favorite* is a specific kind of verb that is typically personal in nature. It's not all that different from bookmarking. Favorites may or may not be public, but the original motivation is to "save it for later" — like a positive flagging. * *like* is a gesture — and may be aggregated across many users — or an individual user (I'm thinking FriendFeed) — to show popularity or inform a recommendation system — but is more casual, temporal and lackadaisical than favoriting. It's definitely a different user intention than favoriting. * *voting up* is also a gesture, but the intention is to have a vote recorded and displayed numerically. The difference between voting up and liking is subtle, but important, largely because of the interface involved. Voting up typically results in a live counter being updated when a user votes something up; when you like something, the change is indicated by the actuator changing (i.e. from "Like" to "You like this"). * *resharing* is what we're really talking about here — and I think the jargon around *retweeting* and *redenting* is actually quite alienating. At every step of the way, you have to think about an interface element ending up in some random UI or application that you didn't design, or that lacks consistent context. I get frustrated enough with Microsoft Word and its ilk for some of the obtuse words it uses to describe things. I think there's something to learn here, and it's to use the most accurate, familiar word to describe functionality as possible. Therefore, if StatusNet is going to offer a specific interface dedicated to *resharing*, it should be called by its proper name and make it easy for someone to complete the task that they wish to complete. As I've followed the conversation around Twitter's retweet changes, I think that it's critical that the reshare functionality not strip out one's ability to annotate the original content with content of their own — even if that means changing the original content to fit within the limitations of a post. Resharing, furthermore, is really the same thing as *forwarding* an email, and it should be treated as such. It just has a different name because the recipient is largely unknown (whereas in an email, you must select your recipients). I'm happy to elaborate further, but wanted to start there. Chris On Sun, Aug 30, 2009 at 1:57 PM, Sarven Capadisli <[email protected]>wrote: > Thinking further about the redent proposal here: > http://status.net/trac/ticket/939 > > We should take care with this feature because adding it would increase > the cognitive load for a notice item. I'd also like suggest that we > review this feature a little further before pushing it out the door as > it will have implications. > > So, here is how I'd define the following actions: > * Favoriting: flagging a notice for personal use (e.g., appreciation, > bookmark) > * Redenting: flagging a notice such that one wants to share it with > everyone > > Some observations: > * Both actions are public. > * Both are essentially vote ups. > * The act of favoriting can be seen as a status in and of it self. > * Redenting is important enough that it should be trackable. > * Favoriting is closer to 'liking', and redenting is closer to > 'spreading'. > > Which leads me to this imperfect idea when a user clicks to favorite a > notice item: > > * add it to user's favorites > * automagically send a notice like "♻ @evan The quick brown fox" and > make it an in-reply-to the original > * if the notice is great than 140 chars (because of the addition of "♻ > @evan " to the original) we can perhaps do some truncating from the end. > > All this leads me to think about the act of sharing. If I click on > something like 'Share', I could redent and add it to my favorites at the > same time. And, what if it gave the opportunity to edit before sharing > (which is a common practise)? > > So, what do you think are the implications for human experience, API, > storage, bandwidth, and ..? > > -Sarven > > _______________________________________________ > Laconica-dev mailing list > [email protected] > http://mail.laconi.ca/mailman/listinfo/laconica-dev > -- Chris Messina Open Web Advocate Personal: http://factoryjoe.com Follow me on Twitter: http://twitter.com/chrismessina Citizen Agency: http://citizenagency.com Diso Project: http://diso-project.org OpenID Foundation: http://openid.net This email is: [ ] bloggable [X] ask first [ ] private
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
