The money part of App.net is a red herring
alexhillman.com
The money part of App.net is a red herring
1–10 of 108 posts
Re: The money part of App.net is a red herring
#2Re: The money part of App.net is a red herring
#3At this point, it seems like there is more people talking about App.net than people potentially using it.
Re: The money part of App.net is a red herring
#4It reminds me of the people you see who write forums posts like 'I just got my first Mac, now what?' when the answer is always 'do whatever you wanted it for in the first place'
Re: The money part of App.net is a red herring
#5That's a pretty callous way to end a post, Alex. It's not either-or. If you really feel that way, ask for a refund. Donate the money to charity whether you get the refund or not.
Re: The money part of App.net is a red herring
#6Re: The money part of App.net is a red herring
#7Re: The money part of App.net is a red herring
#8Re: The money part of App.net is a red herring
#9Re: The money part of App.net is a red herring
#10Most people, especially on HN, pointed to the way "Dalton handled things" as the reason for wanting App.net to succeed. What drives the majority of the activity on App.net are these continuing discussions of what App.net could be, how fantastic it could be and what are the various kinds of pains it would solve. In fact, these very same conversations are as generic and ambiguous as the way that I describe them. Very few specific points are brought up, but rather, there are these sweeping discussions taking place on the platform.
I'm kind of curious whether what Dalton is trying to do with app.net is only capable of being accomplished with Twitter and with Twitter only. This is considering Twitter's userbase, Twitter's 3rd party app ecosystem, Twitter's traction and Twitter's history.
My point in saying this is that, it's impossible to recreate all this with another service (app.net). They are starting from scratch not only in function, but in context. I'd argue this is what's leading to the ambiguous dynamic and cloudy future for the service.