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.<p>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.
Netbot is causing quite a stir at app.net. Here's a word cloud of the past hour's global timeline:<p><a href="http://adn.loqix.com/appwords.17:00-03.10.2012.png" rel="nofollow">http://adn.loqix.com/appwords.17:00-03.10.2012.png</a>
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.
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.<p>Ifttt fails because it does not allow proper link posts to facebook, and going through twitter to facebook results in truncated messages.
Bought it, have it sitting right above my Tweetbot app.<p>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.