News for hackers. Stuff that matters.
Re:The Great App.net Mistake by spullara on Tuesday August 20, 2013 @07:42PM (#6247327)
At that point wouldn't you be better off using a bigger social graph?
Re:The Great App.net Mistake by bigiain on Tuesday August 20, 2013 @08:42PM (#6247523)
Yes - if you could get access to "a bigger social graph" without risking the owners of those bigger graphs shutting down or limiting your api keys, competing with you directly after you've proved/developed a market, or any of the other "dirty tricks" Twitter/FaceBook et al. have pulled on developers.

(Note: app.net might pull those dirty tricks in the future, but at least they've got a business model that doesn't _require_ them too)

Re:The Great App.net Mistake by neuroscr on Wednesday August 21, 2013 @02:14AM (#6248494)
Twitter only allows you access to 100k users or so (tokens), and your business is at risk of being turned off. or App.net providers you access to 150k+ users growing user base. Plus an a free sign up, access to hosting for file storage, and permissive messaging.
Re:The Great App.net Mistake by spullara on Thursday August 22, 2013 @12:23AM (#6255160)
IMHO that is only true if you want to be a Twitter clone or otherwise be in the same business as Twitter.
Re:The Great App.net Mistake by terhechte on Wednesday August 21, 2013 @02:41AM (#6248569)
Not if you want to leverage an already existing social graph, so that people have to sign up for one service less.