Comments by Joshua Kaufman
Reply | Original | Permalink | TweetTesting 1 2 3
Reply | Original | Permalink | TweetDon’t forget about LaLa, which works similarly to Imeem and Simplify Media, but is more about the “music in the cloud” and unlike Simplify it doesn’t require my machine be on. I’ve recently uploaded my entire library to LaLa (they already had most of my tracks do I didn’t have to upload them) and the experience of being able to listen to my music wherever and whenever has been great – a major leap forward in web-based music as far I’m concerned.
Reply | Original | Permalink | TweetOh I loved this movie. Just amazing in so many ways.
Reply | Original | Permalink | TweetYes, please.
Reply | Original | Permalink | TweetI just wanted to pop back here to say thanks for encouraging me to jump ship. The only RSS feeds that I read now are activity feeds: changes on our company wiki, friend activity on Upcoming, link to my blog and other important things I manage.
I used to read ~25 - 30 blogs on average every day, but you made me realize that I wasn’t getting much value out of them at all. Compare this to Twitter, where I get bits from the blogs I use to read, friend updates and conversation, which is incredibly more valuable. I think I’m saving about 30 minutes to an hour every day because of this change, and in these times, that’s a lot.
Thanks, and keep on inspiring!
Reply | Original | Permalink | TweetSome good points here that I've been thinking about for a while. Your answer to the second question alludes to another important question: how can we keep from trying to read everything? Well there are several answers to that, but the good news is that, as designers, we can control the experience to a large degree and make feet dipping easier. One of the simple ways to do that is to remove read/unread status from items.
I use EventBox as my desktop feed/Twitter app and I've been working with the developers to do just that:
http://getsatisfaction.com/thecosmicmachine/top...Coincidentally, I used the exact same metaphor of the "stream." Great minds think alike, eh?
(For a more conversationally focused look at streams, take a look at Stowe Boyd's writings on the topic: http://www.stoweboyd.com/message/2008/03/beyond... )
Reply | Original | Permalink | TweetSo what you're saying, in short, is that if any other service allows @username to reply/demark/notify users on that service, they shouldn't be publishing those updates to Twitter.
I like Twitter, but to play the devil's advocate for a moment: you're barking up the wrong tree. Just because Twitter was first and currently has the largest number of users, does that mean that everyone else who came after them is doing it wrong? @username syntax is quickly becoming a standard for notifying/demarking users on a service. Publishing to Twitter is quickly becoming a standard for communicating social services activity.
Yes, Twinkle hijacks Twitter usernames. But yes, it could happen on any other social network, and not just a social network like Twinkle that mimics Twitter.
If there's one thing that's definitely broken here, it's the design of Twitter @username replies. If they didn't want usernames to be hijacked, they shouldn't have allowed publishing to Twitter via their API.
Reply | Original | Permalink | TweetHello. I'm having lots of sign in issues with bit.ly. How can I contact the bit.ly team? (You guys need to make "contact us" a lot easier to find!)
Reply | Original | Permalink | TweetFabulous news. Looking forward to seeing the new space!
Reply | Original | Permalink | TweetI'm not trying to make your life difficult, but I changed the URL schema again tonight. Sorry :/ http://unraveled.com/archives/notes/2008/12/the...
Reply | Original | Permalink | TweetSorry I changed something on my site that broke some links. The new link is:
http://unraveled.com/archives/notes/2008/12/18/...
Reply | Original | Permalink | TweetOkay, you’ve pushed me over the edge. I’m doing it. I’m taking the plunge. I’ll stop using my feedreader as of today. Godspeed.
Reply | Original | Permalink | TweetIntegrate. Integrate. Integrate. The services are making it easier to do so these days, and with so many bits floating about it’s becoming more critical if you want to maintain your sanity. Here’s how I keep my posting context together at the moment:
I use Twitter for the immediacy of posting quick updates, comments and replies. If those thoughts are more well formed and not time sensitive (like replies), I usually try to post them as “notes” on my blog, unraveled, and use TwitterFeed to automatically import them into Twitter. For more mature ideas and commentary, I’ll post them as an “entry” on my blog. Entries do not get synced to Twitter as the content is lost with the 140 character limit. Blog posts happen rarely enough that I’m happy to tweet them manually. I use the Twitter Facebook app to sync my tweets (and accordingly my blog notes). Beyond this I generally don’t post to Facebook.
The aggregating/reading context of all these bits is just as interesting, but I’ll save that for another post.
Reply | Original | Permalink | TweetHooray for Children’s Book Text!
Reply | Original | Permalink | TweetAAC is the default import encoder so hopefully most folks don’t have to go through these steps to get that option in the contextual menu.
