After much discussion around the @replies subject I started thinking about a system that could automatically resolve social network addresses no matter where they appear. I then decided to try the approach of writing a Chrome extension that could do the job.
The DecentralizedAddresses extension is in development and is available on github for anyone to contribute. As my JavaScript skills are not very good, any help would be highly appreciated.
I just stumbled on a Buzz by DeWitt Clinton about a possible solution to the use of decentralized @replies. From the Buzz:
I want to throw some ideas out there about how it can someday be done in a decentralized fashion using open technologies such as WebFinger, Portable Contacts, AtomPub, and Activity Streams. (And maybe Salmon. Read on.)
The proposal would let you address any user of any application in a complete decentralized way.
And not only is this process fully decentralized (i.e., there doesn’t need to be a Google in the middle), it delegates very well, so that domain owners wouldn’t have to implement it themselves — but they could later if they wanted to.
Just a quick note to archive the way Google Buzz is using the @ syntax. From “Google Buzz Tips“:
If you’d like to send a private message to someone, type @ and use Gmail’s autocomplete feature to find the email address of your contact.
In practice, you address other users by typing an @ symbol followed by their e-mail address, like @user@example.com. This is exactly what I proposed a while ago as an easy way to address any user on any Web application:
Afterthought question: can this microsyntax be expanded to @user@application so that we can finally address any user on any Web application easily. I’m thinking about that.
For now, you can only send messages to other Google Buzz users but I’d expect this syntax to be used to address users of other supported destinations (twitter et al).
Great post by Pedro Pinheiro about making a business around art. I particularly like this excerpt:
For free? Why?
Because the money to be earned is not on things that can be copied. That’s a lost battle. If you’re a musician, you can make more money on concerts and events. If you’re a photographer, more money can be made by shooting specific assignments for customers, or on photography workshops. If you’re a writer, you can make more money by participating as a speaker at conferences. The era of making something and just making your livelihood from just that is nearing its end. And getting your creations known to the widest possible audience is the key for getting work that can’t be replicated.
Read the original: Pedro Pinheiro: My artist’s manifesto.
Stowe Boyd writes about a possible approach to address different user profiles on different clients. After exposing a possible microformats based approach he talks about a microsyntax solution to the problem:
A microsyntax approach would be something visible in the stream, like including a prefix in front of an @mention or retweet to denote original or desired client:
dabr@pigsonthewing Nice profile!
Here, the implication is that I am referring to Andy’s profile on the Dabr client.
I disagree with the proposed syntax format and propose a new one: @user@client. Here’s my rationale behind it:
Afterthought question: can this microsyntax be expanded to @user@application so that we can finally address any user on any Web application easily. I’m thinking about that.
Read the original post: Twitter URLs: Are Microformats The Answer To A Real Problem? on /Message.
Great news:
the Cliqset FeedProxy tool will normalize feeds from more than 70 other services into new feeds in the ActivityStreams format. It may just be an initial inroad to interoperability between these networks, provided by a 3rd party and not yet extensively used – but it’s an important step none the less.
Read the original: The Day The Highway Went Coast-to-Coast: 70+ SocNet Feeds Normalized by New API on ReadWriteWeb.
In order to actually make a dent in Google’s market share, Bing would have to pay such exorbitant sums to so many different news companies that it would be difficult to recoup its investment. Bing certainly get some marketing buzz out of any such move, but that’s about it.
Here’s a list of links about this:
Read the original post: Bing Tries To Buy The News on TechCrunch.
That was about time! They added Lisbon and a bunch of other cities around the world. I’m finally using the Android application and, so far, I’m enjoying it.
Check out my foursquare profile and friend me!
You say:
My sense is that cross-platform following can mostly be achieved by RSS subscription, although following does include a notification aspect. For example, in both Typepad and Tumblr I can expose the list of those that I am following, and those that are following me. Various platforms need only to notify each other of following and unfollowing, and the identities involved, and then cross-platform following semantics works.
I agree with using RSS subscription as a cross-platform following mechanism but I’d stop there. If you’re gonna use RSS over HTTP then you can use the unique visitors metric as your “followers” count and the referrer information to find out who those followers are.
This, of course, only makes sense if you have a ready to use application that manages all those metrics for you.
Read the original: More On Cross-Platform Tumbling: Following Is Mostly RSS on /Message.
This is a post to test a communication flow using a feed reader and a blog post as a “distributed twitter”.
Read the original story: Where is RSS? on Scripting News.