Post

Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API. We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent. Full details: github.com/mozilla/stan...

github.comPrompt API · Issue #1213 · mozilla/standards-positionsSpecification title Prompt API Specification or proposal URL (if available) No response Explainer URL (if available) https://github.com/webmachinelearning/prompt-api/blob/main/README.md Proposal au...

Anna Willoughby

@akw.bsky.social

30 Apr

Didn't Firefox get caught hiding code commits from LLMs though or did I misunderstand that bit of news

Firefox for Web Developers

@webdevs.firefox.com

A misunderstanding, I think github.com/mozilla-fire...

github.comBug 2011195 - When an agent commits, don't add itself as author r=ai4… · mozilla-firefox/firefox@71cc24b…dev-reviewers,suhaib DONTBUILD Differential Revision: https://phabricator.services.mozilla.com/D279515

30/4/26, 12:55 pm0 reposts1 like

Anna Willoughby

@akw.bsky.social

2 May

Is that not an attempt to hide LLMs making their own commits

Firefox for Web Developers

@webdevs.firefox.com

3 May

No, it's forcing humans to take responsibility for their contributions, regardless of _any_ tooling that was used in producing that contribution. We don't let autocomplete or linters sign commits, and that doesn't change with AI.

Anna Willoughby

@akw.bsky.social

3 May

You shouldn't let ai commit without a human period, but if you're going to it should really be marked in some way.

Firefox for Web Developers

@webdevs.firefox.com

4 May

No - we require a human to take responsibility, no matter how the code was written. If we use something like `git blame`, we want to see the human that took responsibility for the code.