Dave Winer praises Dropbox technology and goes further by suggesting that everyone should be able to run their own private servers:
(…) the technology that Dropbox has mastered is so important that there should be an open source equivalent that we can all deploy, so we can have Dropboxes for sensitive info we don’t want to share with them (…)
I’m a happy Dropbox user myself and I went looking for options. Well, there isn’t an out-of-the-box open source equivalent to Dropbox but you could easily build one:
Now we have is a simple Dropbox style app that is lightweight, with a functional back-end running rsync, which is a known stable app that will scale, and while it doesn’t provide the front-end and web view that Dropbox does, that could be an easy part for a UX developer to tackle (…)
Read the original post: Afternoon sellout notes.
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:
- It doesn’t break any functionality (just like the proposed syntax): user will still be able to see this tweet as a mention;
- It adds new functionality: if client is also a twitter user it will also be able to see this tweet as a mention and act upon it, if desired;
- It’s more meaningful than the proposed syntax: you can read it as “user at client”. In the original syntax, saying “client at user” just seems awkward.
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.
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.
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.