Question thread #37

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[syntheid]

Out of curiosity, what's the current state of Dreamwidth's APi? I saw there were some discussions about creating a new one and deprecating the xmlrpc, but I couldn't tell if any progress was actually made on that.

[denise]

It's being worked on!

[me_and]

It is!? Is that work happening anywhere I can see? Planned changes to the API are relevant to some of the design/spec work I'm currently working on (or at least working on when I'm sufficiently sane to do so).

[denise]

sooo, over the past six years, every time we've kicked off a conversation about the API redesign it gets bogged down in details and people argue about all the little things and the conversation dies off either because it gets bikeshedded to death or because the person who decided to take point on it realizes the scope of the work that needs to get done and runs far, far away. (This is why it has been six years with no movement!)

This time around, somebody who wanted to work on a particular project realized it would only be possible with a more modern API, and we decided that we would try it the other way this time: first version of API v2.0 (minimum viable for that project, etc) done as part of that, and then we open it up for discussion and collaboration and the like after that.