Entry tags:
Question thread #57
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.
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.
no subject
(no subject)
no subject
1. It lets me post preformatted HTML5, with unclosed [p] and [li] tags, and treats newlines as spaces as per the HTML spec. This probably rules out XML-RPC unless it will take the body of the post in a CDATA section.
2. The body of the post comes from STDIN. (I can write a temporary file if necessary, but I'd rather not.)
3. After it posts, it returns the ID of the post.
4. Ideally, it can edit a post.
5. It can be put in a Makefile or other shell script -- it mustn't ask the user for the password or borrow a cookie from a browser. I want to integrate it with my make- and git-based workflow.
If there isn't one, which API should I use to build one? I've been meaning to find one of these for a while; it's gotten more urgent now that my preferred client, ljupdate.el, stopped working presumably due to the HTTPS upgrade.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
(no subject)
no subject
When I attempt to crosspost I get this error message:
fiddlingfrog @ www.dreamwidth.org: transport error - HTTP status code was not 200from the JournalPress plugin. The other plugin does not give me an error message.
Does anyone know where I should start looking in order to update either plugin to work with the current https configuration of the site?
(no subject)
(no subject)
(no subject)
no subject
(I'll eventually go paid again, but that won't be for a while due to RL.)
*edit*
If you're concerned about people swapping which 15 all the time, force it to only be changeable like....1/year or 1/6 months? I don't know if a limitation like that is even possible.
(no subject)
(no subject)
(no subject)
(no subject)