Re: Twitter URLs: Are Microformats The Answer To A Real Problem?

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:

  1. It doesn’t break any functionality (just like the proposed syntax): user will still be able to see this tweet as a mention;
  2. 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;
  3. 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.


Focus on your active users

Quoting The Difference Between Total Users and Active Users:

It is not a problem for a service to have a large group of non-active users if they have a large group of active users. It’s the latter group that you need to focus on. Over time, I’ve learned that many non-active users become active for one reason or another. But they don’t become active by focusing on them. They become active because you focus on the successful users and make them even more successful.

Here are some thoughts to focus on your active users:

  • promote what they’re doing, either through your application or explicitly through social media;
  • ask them for a review of your application and publish it, word for word, on your blog;
  • offer all help you can whenever they want to do a meetup about your application;
  • ask for their opinion before launching a new feature;
  • give them credit about new ideas you implement, whenever appropriate.