Joe Aston wrote:
Development effort aside, is there an argument /not/ to make the
Twitter-like API a module too?
The main argument is that a) it's self-contained doesn't require
integration with other services and b) it's very, very useful.
The main reason to move something out to a plugin is if someone might
want to turn it off. I haven't heard of anyone wanting to disable the
API so far.
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.
But people can do that now! I'm working on an AtomPub plugin, for example.
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.
Yes, file upload (as well as conversations and groups) are a high
priority for adding to our existing API.
-Evan
--
Evan Prodromou
CEO, StatusNet, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
