4 ms·
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 u
by bradleyjoyce 14y ago
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.
- whalesalad 14y agoYeah 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.
- swilliams 14y agoI'm pretty sure the newer TOS for Twitter precludes that.
- deleted 14y ago[deleted]
- gjulianm 14y agoThe TOS just forbids mixing Twitter updates with updates from other social networks in the same stream, I think.
- nitinthewiz 14y agoPeople can post from Netbot to both twitter and App.net. Twitter's TOS doesn't allow the twitter app to post to anything else...
- jeffgreco 14y agoTwo apps = two purchases.
- ceejayoz 14y agoIf nothing else, the extra revenue can't hurt.