Question thread #147

[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

This might be a bit long

[brickhousewench]

One of my very few regrets about Dreamwidth is that there is no app for it, so it's just about impossible to read on my phone. I seem to remember reading at some point that the reason there is no apo is because the Dreamwidth API would need to be completely rewritten. Which makes perfect sense, I'm sure that's a huge amount of work.

In my day job I am a software Technical Writer. And my company is ALL IN on using AI and LLMs to accelerate everything and has not put any limits (yet) on spending/tokens. While I'm not a developer, I've been quite impressed with what I've been able to accomplish using Cursor to read the code base and answer my questions. I recently had Cursor read the code base for error messages and generate troubleshooting documentation, and was very impressed with what it produced. And most of my feedback from my engineers when they reviewed my PR was "I would delete that, we don't want to tell customers that." (That is, it's not wrong, we just don't recommend that.)

So my question is, have you considered using artificial intelligence to revise the API and write an app for Dreamwidth? If it's a question of money, I'm sure I'm not the only one who would be willing to buy some AI tokens if it means we might get a Dreamwidth app.