Question thread #148

[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

How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[pauamma]

I see it in most if not all recent changelog entries, and since it hasn't been discussed where I could see it, I don't know whether it's opt-in, opt-out, or (worst of all as far as I'm concerned) mandatory. Can someone who knows explain?

(For clarity, I do not object to someone else using Claude or any other A"I" to modify code I wrote once it's been committed. The GPL license terms preclude that objection. I do not, however, want code I wrote myself to be attributed to anyone but me, or unclear in authorship.)

Re: How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[cesy]

Entirely opt-in, it only shows if you've chosen to use Claude when writing code.

Re: How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[pauamma]

Thanks.

Re: How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[pauamma]

Relatedly, https://www.congress.gov/crs_external_products/LSB/PDF/LSB10922/LSB10922.8.pdf crossed my Mastodon timeline today.

Re: How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[mark]

This space is super interesting and I'm very curious to see how it evolves. Given the way these AIs seem to be created (using all sorts of materials), I would not be unhappy with an outcome where you can't copyright what they make -- seems like it might be only fair.

Re: How not to use that "co-authored-by Claude" thing I've been seeing in changelog lately?

[mark]

Exactly this!

I am using it when there are old (multi-year old) PRs that I want to get merged, and then I'm having it help with writing the code. But the person still gets credited, along with Claude, since both contributed.

For PRs that are "newer", what I've been doing is leaving a review (which Claude sometimes helps with) but then it's up to the author what they want to do.

[etfb]

Has anything changed about the Dreamwidth interface/flat API? When I post to the LiveJournal equivalent with mode=sessiongenerate and a deliberately wrong password (for testing purposes), it gives me an error as expected:

errmsg
Invalid password
ljsession

success
OK

When I do the same to the Dreamwidth URL, it gives me this:

errmsg
Client error: No mode specified.
success
FAIL

I'm using Postman for testing, and putting the parameters in the Body section as form-data. As I say: works fine with LJ, not with DW. Any hints on what I should be looking for?

[etfb]

Interesting: I tried x-www-form-urlencoded instead of form-data, and it went through OK, even when I put in the correct API key/password. So it looks like a recent change has made DW decide to only accept that one content type where previously it accepted the other, or maybe even both.

Making required changes to timmc/ljdump v2.0.0 to see if this works there too...