This isn’t Mozilla taking a stance against AI.

It’s them articulating clear and logical reasons why the proposed API, in its current state, is bad for web interoperability.

▲ ilaksh 2 hours ago | parent | next [-]

Did they propose a specific alternative (non-extension) API?

▲ jedimastert 2 hours ago | parent | next [-]

Why would they? This is an issue put up on the "standards-position" repo. They requested a position on a proposed standard, and Mozilla gave it.

▲ rafram an hour ago | parent | prev | next [-]

There’s one obvious alternative:

   fetch("https://api.openai.com/v1/chat/completions", { ... });

	▲	ilaksh an hour ago \| parent [-]
		Right and that means people have to send their data to an external service. Give it X months (or years??) and people will realize this is actually a privacy/data autonomy issue. It's just dominated right now by the anti-AI/anti-technology sentiment in the west. That will gradually go away as more people use AI and robotics and realize how wrong they were about it.

▲ madeofpalk 2 hours ago | parent | prev | next [-]

No, that’s not how this process usually happens.

▲ aljaz823 2 hours ago | parent | prev [-]

Why would they need to?

▲ hatmanstack an hour ago | parent | prev [-]

So I guess the question would be, "What makes this acceptable Tech". I don't know how you get there without offering some type of "Search" like choice for open models. We all know how that turned out.

Maybe Mozilla can save itself by getting paid to serve Google's model as default rather than another providers. Would replace the revenue stream they lost.