(1) sounds like a derivative work, but (2) is an interesting AI-simulacrum of a clean room implementation IF the first LLM writes a specification and not a translation.

Where do derivative works fit into your model of copyright?

It's not "my model." If someone paraphrases a poem, and publishes that paraphrase, the original author will not be able to sue. (Or rather, they can sue, but will almost certainly lose.) There is a body of legal precedent for each category of work you can imagine, and each has come to have its own criteria for what the threshold is for being derivative vs a unique re-expression; but I am confident from how that has played out and from the fact that it is well accepted that code tends to be comprised of only so many patterns, that a codebase that is reverse engineered based on prompting alone will not be considered a derivative work.

It's obviously an opinion. But I'm confident enough in it, as are, say, Lovable and such companies, that I/they are willing to concretely operate on the hunch that that is how it will play out in court if ever the hand was forced.

Usually through enterprise social media management apps. Hootsuite is the first that comes to mind, I'm sure there are many more. But I don't know what the auth looks like underneath that, an API for sure, but whose token?

I care! I have to cross-reference multiple apps to get a good detailed forecast, a "minutecast" of precipitation, and Canadian humidex and windchill numbers. I haven't tried this one yet because I'm a little confused why it didn't offer me a free trial, but if it gives me all of that then I am sold.

I think it’s a bug for Canadian users as it doesn’t offer me a trial either. Or they just don’t do trials here.

.gitkeep has no meaning to Git, only to us meatsacks that recognize the name. As far as Git is concerned, it's just another file.

From the perspective of research ethics: it is very much without permission in that situation

I like(d) LocalStack fine, but you've got the same kind of problem that Minio has.

> As a result of this shift, we cannot commit to releasing regular updates to the Community edition of LocalStack for AWS.

https://blog.localstack.cloud/the-road-ahead-for-localstack/

That’s fair. There’s still a free tier that you can use.

https://blog.localstack.cloud/the-road-ahead-for-localstack/...

But IMO, LocalStack community’s S3 service is pretty stable, so I’m doubtful there’ll be much parity drift in the short to medium term.

I found myself wondering where the rest of it went.

The balance sheet write-off.

I think it was more of an intentional tradeoff, as one of the many goals of CT logs was to allow domain owners to discover certificates issued for their domains, or more generally for any interested party to audit the activity of a certificate authority.

What you're describing there is certificate... translucency, I guess?

Yes, "translucent database" was exactly the concept I thought of when asking the question. The concept is keep access to specific items easy but accessing the entire thing as a whole more costly.

But whose monkeys are these?