Hacker Read

Camillo | karma 3406 | avg karma 3.17 · 2013-08-02 07:53:47+00:00

I was thinking of making a Facebook chat client as a fun project, but this post made me reconsider.

eksith | karma 5196 | avg karma 3.31 · 2013-08-02 08:30:52

You can do something with Twitter instead. No reason to completely drop a project if the first place you look to host it doesn't seem appealing.

Twitter has their share of warts, but they're markedly different when it comes to the speed of "breaking things".

Something to keep in mind though: You're working with someone else's platform which means you participate at their pleasure. Any API provider can do whatever they please with their product so try to decouple API handling from the rest of your client as much as you can so you can reduce the likelihood of being pulled by the tides.

reply

mjn | karma 9588 | avg karma 5.24 · 2013-08-02 10:07:15

The OAuth bit in the title of this post reminds me that that change broke one of the author's previous projects on Twitter: http://www.bogost.com/blog/it_soared_a_bird.shtml

Twitter's responsibility does seem somewhat less, anyway, in that they've never been as platformy as Facebook: Facebook actively claimed that this was a place to deploy your games and other apps, but then broke stuff constantly.

reply

JonnieCache | karma 17245 | avg karma 4.71 · 2013-08-02 11:17:09+00:00

Just be traditional and build a foul mouthed IRC bot. It's a tried and tested way to enjoy yourself and exposure a new socket API.