Menu
▾
▴
#13 API
A really simple API is needed. It should be really bare-bones and fast.
Perhaps something like an RSS feed of changes, with an ID by which one can track to which category (chat, user comment, etc.) the content belongs to and a way of recognising which chat items belong to the same chat.
Also open to simpler ways of doing it as you probably have some thoughts on this one already.
Highest priority to design this, lower priority to implement, but still important.
Standard APIs should be automatically generated by Kapenta, with various options including RSS. Some, such as chat, will have to be created manually. Propose adding a 'bot' class of user authorised to use these interfaces. An additional authentication mechanism will need to be implemented for RSS readers since they do not use the login form (and few RSS readers support cookies).
Ok. Add bot class, by all means.
NB: Please, assume Cookies are ON. This is not meant for RSS readers as such, but for automated processes. We can also use atom instead of RSS if you prefer.
Propose implementing HTTP digest authentication for APIs. This will allow a measure of security on private data and securing of RSS feeds - which in the long run I hope to implement for 'my feed', blogs, projects, and most importantly admin tools. This will also ease general automation since digest is supported by wget/curl/etc.
More RSS readers support basic HTTP AUTH header, but is discouraged for reasons discussed RFC 2617, section 4.
ps: cookies will always be an option, since that is the default auth.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Reopened, because it has not yet been implemented.
The latest news on this is that the interface will jointly be designed with the German team, so I am setting the priority way down.
How is this progressing?
It is important to close this now.