Development effort aside, is there an argument *not* to make the Twitter-like API a module too?
This would allow people develop and use their own add-on API interfaces; e.g. an API "done the right way", a SOAP-style API, or maybe even a minimalist-style API for reduced data transfer. I agree that functionality like File upload should be part of the core, but this is the kind of feature that should also be accessible through an API method. On Sun, Sep 27, 2009 at 4:02 PM, Evan Prodromou <e...@status.net> wrote: > So, we're moving the following features from "core" to modules in 0.9.x: > > - Twitter integration > - Facebook integration > - Jabber integration > - SMS-over-email > - OEmbed > - OpenID > - Various URL-shorteners > > Thing we're leaving in as core: > > - Twitter-like API > - File upload > > Does this sound about right? > > -Evan > > -- > Evan Prodromou > CEO, StatusNet, inc.e...@status.net - http://identi.ca/evan - +1-514-554-3826 > > > _______________________________________________ > StatusNet-dev mailing list > StatusNet-dev@lists.status.net > http://lists.status.net/mailman/listinfo/statusnet-dev >
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
