No, everyone I know literally pronounces it as ecma script.

Yes, but why is it evil?

I think that part is a reference to a Futurama episode where a holodeck malfunction materialized several villains, including "Evil Lincoln".

Ah if that's the case, then that makes more sense. Thanks!

What is curious to me is that there's a possibility that a single plant in conjunction with natural oscillations caused enough trouble to start a doom scenario.

Oscillation -> damping -> possibly faulty equipment and possibly lack of power plants to absorve the reactive load -> 0 voltage in two countries and some neighbouring regions

There's also the possibility that Portugal put too much demand on the market due to negative prices, but I'm not sure if it was explained how much that had an effect on the whole thing.

If this is going to be Linux phone, then a good use case would be to use it on desktop mode with an external monitor. They mention this on their website but they are planning on doing it with a convuluted wireless device?

Why not simply usb C with displayport alt mode?

I could just stick a dongle in there and connect all my peripherals. It's not new technology, that's what I do with my 3 year old phone.

Taken directly from the interview:

> Does one (or both) of the USB-C ports support DisplayPort Alt Mode, so that I can plug into a display without carrying accessories? > > Yes, at least one of the ports will provide direct DisplayPort output, allowing you to use the Nexx as a desktop without additional docks.

So indeed, it's going to have displayport!

I'm guessing their wireless dock is optional.

These are the kind of figures the EU should be looking at. Not the meagre hundreds of millions.

It's 32B€

Tldr because this article has way too much fillers to my taste (but I'm sure there are people out there that enjoy reading that kind of thing):

The native Instagram and meta apps start a server listening on predefined ports when you launch said apps, they eventually run on the background as well. When you are on your browser, whether in private more, not logged, refused or disabled cookies, or anything else that might make you feel like you are not being explicitly tracked, the browser will connect to the locally running servers through webrtc and send all tracking data to said servers from the browser.

The android sandboxing thing is basically about how Android isolates each app and should only allow communication through android intents that inform the user of such inter app communication, such as sharing photos and the like. In this case, the browser is communicating with Instagram and Facebook apps without letting the user know.

The legal infregement here is that this happens even when you refuse to be tracked, which is a violation of GDPR and another law mentioned in the article.

The 32B figure is a theoretical maximum (but they also mentioned 100B+ in the article, which confuses me).

And according to the article, they're using RTC because Android is meant to be hardened against backdooring localhost, but Meta found a loophole that allowed it if over RTC.

The technical details roughly boil down to "your browser lets internet sites talk to local services"; in this case if they cooperate they can identify each other, but cf. https://mrbruh.com/asusdriverhub/

In practical terms this is a privacy leak a couple bits more informative but slightly less robust than "these requests are coming from the same IP address."

Does anyone know how long was this going on, are we talking weeks, months or years?

Yep I see it like that as well, code with 0 or very close to 0 interactions from humans. Anyone who wants to change that meaning is not serious.

I think both you and the OP are ends of the same spectrum.

> the model’s only options were blackmail or accepting its replacement

It was not explicitly told to do so, but it certainly was guided to.

It still could have pled, but it choose blackmail 84% of the time. Which is interesting nonetheless.