I'm actually okay with twitter only having 12 users (plus me) - just as long as they are the correct 12 users. So far, 5 of the 12 have committed to using App.net.
I'm a relic though - I make a lot of use of skype-chat/AIM/SMS/iMessaging for my DMing - very little goes through @messages on twitter. For those who do all their messaging on twitter, broad uptake might be more important.
I'm hoping that App.Net establishes an equilibrium somewhat similar to to http://en.wikipedia.org/wiki/The_WELL - in which a dedicated paying community of 5,000 to 10,000 is more than enough for viability - particularly as I think this 5-10K users will be among the most interesting on the internet, and will almost certainly avoid the "September Problem."
Regardless - it's something new, with a working Alpha, with an API, and an interesting group of people, lead by someone with a track record of Getting Things Done. The next year, at the very least will be interesting.
I'm a relic though - I make a lot of use of skype-chat/AIM/SMS/iMessaging for my DMing - very little goes through @messages on twitter. For those who do all their messaging on twitter, broad uptake might be more important.
I'm hoping that App.Net establishes an equilibrium somewhat similar to to http://en.wikipedia.org/wiki/The_WELL - in which a dedicated paying community of 5,000 to 10,000 is more than enough for viability - particularly as I think this 5-10K users will be among the most interesting on the internet, and will almost certainly avoid the "September Problem."
Regardless - it's something new, with a working Alpha, with an API, and an interesting group of people, lead by someone with a track record of Getting Things Done. The next year, at the very least will be interesting.