This. I don't think App.net would have worked a year ago, maybe even not six months ago. But now, with Twitter actively attacking their developers, I imagine we'll be seeing a ton of ports from Twitter to App.net.
Twitter definitely considered the risk of cutting off their development community, but I don't think they intended to hand those developers off to a competing platform. Good timing from App.net.
App.net will get lots of hackers and people in our community, but in terms of reaching critical mass ... I don't think it will work.
People join twitter now out of societal pressure. "What is this thing? What is this ad on the subway that says I should follow them on twitter? Who's this athlete that is now Kobe Bryant with a strange @username at the end of his name?"
Developers, techy individuals, and people who consume twitter at a high level are more inclined to pay for it.
People who casually use it to help trend the latest hashtag about #whatmenreallywantfromawoman could care less. They're not going to pay a yearly fee for this, especially when the line between this and twitter is very blurry.
p.s. I am an app.net user and own a copy of netbot.
I think the App.net guys made an astute observation that the biggest hurdle to attracting developers was doing away with the perception as the platform as a gamble for developers.
It doesn't hurt that the Tapbots guys used the Tweetbot apps to piggyback on, of course.
Just because it's money? You're also spending your time, effort, attention, and opportunity cost.
Is college meta because you spend money to work for free with people who also spend money, while learning from people who get paid money to teach you?
You're probably more used to services that monetize with ads, and encourage quantity of accounts at the expense of quality because it's good for their numbers. Nothing meta about one or the other.
I'm curious as to why they created a completely separate app. Why not just integrate App.net functionality into Tweetbot? I'd certainly be much more likely to use it that way... and I even paid the $100 developer fee for app.net.
Yeah they're essentially identical platforms in terms of interaction. Reading a stream, replying, retweeting/reposting etc...
They already have multi-user support, I'd rather interact with one app in this way. Or better, have the client merge your two accounts so that app.net/twitter become seamless and instead of thinking about who is on where, you simply enjoy it through the window of your client and none of that matters.
But.. I'm sure it took some good work to develop this and by simply updating Tweetbot they might not get reimbursed for that dev time. Rather, the new app must've been required.
I look forward to an integrated client down the road.
This looks awesome! I was wondering how long it would take for companies with Twitter clients to port over to App.net. The App.net platform looks like it may give Twitter a run for its money.
My favorite client in the new frame... I wonder how much time did take to port the network code to App.net? And if using a different key for crossposting.
I'm an AppNet user, but pretty limited in frequency. The primary reason is that I want proper posts to facebook and don't want to post in two places. I would like to see apps like this have the option to cross-post to facebook and twitter.
Ifttt fails because it does not allow proper link posts to facebook, and going through twitter to facebook results in truncated messages.
They have committed to supporting open standards like Activity Streams, PubSubHubBub, and Webfinger. While not OStatus explicitly, it looks like the majority of OStatus will be supported.
[+] [-] colinsidoti|13 years ago|reply
Twitter definitely considered the risk of cutting off their development community, but I don't think they intended to hand those developers off to a competing platform. Good timing from App.net.
[+] [-] whalesalad|13 years ago|reply
People join twitter now out of societal pressure. "What is this thing? What is this ad on the subway that says I should follow them on twitter? Who's this athlete that is now Kobe Bryant with a strange @username at the end of his name?"
Developers, techy individuals, and people who consume twitter at a high level are more inclined to pay for it.
People who casually use it to help trend the latest hashtag about #whatmenreallywantfromawoman could care less. They're not going to pay a yearly fee for this, especially when the line between this and twitter is very blurry.
p.s. I am an app.net user and own a copy of netbot.
[+] [-] kmfrk|13 years ago|reply
I think the App.net guys made an astute observation that the biggest hurdle to attracting developers was doing away with the perception as the platform as a gamble for developers.
It doesn't hurt that the Tapbots guys used the Tweetbot apps to piggyback on, of course.
[+] [-] drharris|13 years ago|reply
[+] [-] diego|13 years ago|reply
Is college meta because you spend money to work for free with people who also spend money, while learning from people who get paid money to teach you?
You're probably more used to services that monetize with ads, and encourage quantity of accounts at the expense of quality because it's good for their numbers. Nothing meta about one or the other.
[+] [-] diego|13 years ago|reply
http://adn.loqix.com/appwords.17:00-03.10.2012.png
[+] [-] johns|13 years ago|reply
[+] [-] 89a|13 years ago|reply
Before netbot that did they ever talk about anything other than "When can we get a good native client"
[+] [-] modernerd|13 years ago|reply
App Store link: http://itunes.apple.com/app/netbot-for-iphone-app.net/id5635...
[+] [-] bradleyjoyce|13 years ago|reply
[+] [-] swilliams|13 years ago|reply
[+] [-] whalesalad|13 years ago|reply
They already have multi-user support, I'd rather interact with one app in this way. Or better, have the client merge your two accounts so that app.net/twitter become seamless and instead of thinking about who is on where, you simply enjoy it through the window of your client and none of that matters.
But.. I'm sure it took some good work to develop this and by simply updating Tweetbot they might not get reimbursed for that dev time. Rather, the new app must've been required.
I look forward to an integrated client down the road.
[+] [-] nitinthewiz|13 years ago|reply
[+] [-] jeffgreco|13 years ago|reply
[+] [-] ceejayoz|13 years ago|reply
[+] [-] astrodust|13 years ago|reply
[+] [-] pgrote|13 years ago|reply
For me, it came down to wanting to be part of something being built from the ground up. Heck, I am not even a big Twitter user.
[+] [-] mikeevans|13 years ago|reply
[+] [-] joeblau|13 years ago|reply
[+] [-] cicloid|13 years ago|reply
[+] [-] aneth4|13 years ago|reply
Ifttt fails because it does not allow proper link posts to facebook, and going through twitter to facebook results in truncated messages.
[+] [-] barredo|13 years ago|reply
[+] [-] timmillwood|13 years ago|reply
[+] [-] abraham|13 years ago|reply
http://daltoncaldwell.com/a-response-to-brennan-novak
[+] [-] kevinherron|13 years ago|reply
[+] [-] primatology|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] DanHulton|13 years ago|reply
That said, it really hides the Global stream, and I'm not really cool with that. There's all kinds of good stuff in there.
[+] [-] thebigkick|13 years ago|reply
[+] [-] lukeholder|13 years ago|reply
[+] [-] dekz|13 years ago|reply
[+] [-] 89a|13 years ago|reply
[+] [-] nitinthewiz|13 years ago|reply
[deleted]