Because of course it does. You are fighting the wrong side, they should proof they are good, not you defend them.

Yeah, it is insane a fully open source firmware with reproducible builds is not a minimum standard for something as sensitive as a modern smart TV.

It is not the minimum standard for computers. Why should it be for TVs?

It should be the minimum standard everywhere.

This is awesome and horrendous at the same time.

First thought after reading “3D map of your codebase” was that now we will be able to code in Johnny Mnemonic style :D

You can buy them overseas from online secondhand stores like mandarake and play on your switch, because there is no region lock. Interface will still be in Japanese, but it is pretty obvious what to to and how.

That “install as app” pop up after the first station is clearly unnecessary and utilises a dark pattern - “not now” button is painted like it is disabled. Please don’t do like that.

This is a good call and has been fixed.

And then government will declare this printer illegal because of no yellow dots.

Good thing they're not selling a printer then, they're selling a parts kit that you have to flash an open source controller firmware to and assemble yourself. Or you may just source them in any way you want. You can't really "outlaw" open source, we had this whole song and dance with https://en.wikipedia.org/wiki/Export_of_cryptography_from_th...

If it needs so much explanation and discussion, maybe it is not a great idea after all?

The article describes the current situation first. The whole explanation is quite simple: QUERY requests are the same as GET, but they have a body.

So just add an optional body to get

The article also addresses why this is not the chosen solution. It's pretty much the first one you'd think of: all kinds of existing software (that can be between client and server and out of their control) already handle GET bodies in all kinds of incompatible ways, because the existing standard says they're meaningless and "shouldn't" be included. The idea is to not break people's stuff, so they don't rugpull the established standard.

There's usually a reason why the simplest solution that pops into one's head is not "just" used by the people who put a lot more thought into it. Not always, but it can be useful to try to come up with it.

So, I need to update all the tools to support QUERY, or I need to update all the tools to support GET/body.

So, either way, I need to update all the tools.

Just fix GET.

The point is that if you do that, you end up with lots of undefined behaviour in existing software that has not been patched yet.

If you make it a whole new request method, existing unpatched software should just respond with "Method not allowed".

Which means you have to structure everything around multiple scenarios anyway.

Yes, but existing software has already been built around the scenario of only accepting request methods you actually handle.

Arguably the only explanation you need is that "QUERY is the same as GET plus a body". The article just explains what GET is and isn't, but that can be implied.

I don't think this requires so much discussion; it is a very obvious and simple addition, IMO.

It doesn't really need that much explanation though. TL;DR: It's GET but with bodies officially supported.

The problem is that it does not. At all.

It was wintel (windows + intel) before. This will be what? Windia? Wintek?

Winvidia

Nvideous

Nvidiows

Nvindows

And now compare not the numbers, but what these countries actually produce, in global sense. Japan produces cars, electronics, medical and precision stuff, cultural exports. And what do Croatia produce? Not even speaking about almost dying Latvia and Lithuania.