Hydro in Norway, nuclear+wind in Finland.

https://www.iea.org/countries/norway/electricity https://www.iea.org/countries/finland/electricity

Very interesting.

I was also reading: https://norwegianscitechnews.com/2019/10/the-way-forward-for...

CPE like wifi router+nat boxes do by default have IPv6 firewall on, so s/can/is/

Amiga: https://wiki.amigaos.net/wiki/Introduction_to_Exec

> The Multitasking Executive, better known as Exec, is the heart of the Amiga's operating system.

> All other systems in the Amiga rely on it to control multitasking, to manage the message-based interprocess communications system, and to arbitrate access to system resources.

Look up trasnferable objects, it's not new. The fetch api can get you ArrayBuffers that you can shuffle around zero copy, besides to webgl buffers, also to web workers.

But minimizing copying or avoiding format conversions doesn't necessarily get you best performance of course.

I had a look, that certainly looks like part of the solution, now I need to get that array buffer from my backend into the browser runtime transferable object.

Is there a comparison to rate of reference errors in other forums?

It's a good idea so it can't take over your dev machine.

But not sufficient since it'll still F over whatever code you are working on resulting in a backdoored app getting deployed + infected dev scripts etc bringing interesting times to your teammates, downstream open source project users, your api keys and cloud credentials getting compromised etc.

The article doesnt' claim it's executed straight up either ("can result") but it's pretty ambiguous:

> When the project is opened, Visual Studio Code prompts the user to trust the repository author. If that trust is granted, the application automatically processes the repository’s tasks.json configuration file, which can result in embedded arbitrary commands being executed on the system.

In the screenshot the task is named "node" - so it's a bit like embedding a malicious Makefile target as a backdoor.

Except harder to spot since it's in a obscure .vscode/somethingsomething json file. (And probably you can easily fool GH Copilot to run it)

Sounds far fetched. There's still the t vs p when pronounced by english speakers which are pretty distinct.

WP on the name origin:

> Jitsi (from Bulgarian: жици, "wires")

Yep, rfc19188 addressing leads to accumulating complexity due to workarounds (end-to-end addressing is simple, there are very good reasons for that design), addressing ambiguity, and various practical security problems.

Though just like with IPv4 most of the time you shouldn't build on assumed-secure internal networks.