rys

He does explain it in his blog post. He changed it after the erratic communication and actions of RC leadership, then after realising what they were really doing, left them to complete their “security audit”, assuming they’d discover it themselves and take appropriate action as part of that. That never happened (which is wild), so he let them know.

They still don’t seem to be in complete control or understanding of the infrastructure they forcefully took control of.

What about the PlayStation OS, which is reportedly based on FreeBSD?

In practice, what gets labelled as the L1 cache in a GPU marketing diagram or 3rd party analysis might well not be that first level of a strict cache hierarchy. That means it’s hard to do any kind of cross-vendor or cross-architecture comparison about what they are or how they work. They’re highly implementation dependent.

In the GPUs I work on, there’s not really a blurred line between the actual L1 and the register file. There’s not even just one register file. Sometimes you also get an L3!

These kinds of implementation specific details are where GPUs find a lot of their PPA today, but they’re (arguably sadly) usually quite opaque to the programmer or enthusiastic architecture analyst.

One interesting thing is they seem to have also cloned the number of stars each repo has on GitHub. At least that’s true for a cursory check of a few that I’ve committed to. If you click on the star count you’ll then see two separate counts for GitHub and GitCode stars.

It’s one thing to mirror the repos, but it’s another to initially misrepresent the interactivity the repo is getting, even if they’re clear about it when you dig in.

Also, how do you authenticate so you can keep committing and interact with the repo to manage PRs and issues if it’s yours?

So was there ever a deal with OpenAI? Nothing in the keynote mentioned them or needs them. If there isn’t a deal, I’d love to know how everyone claiming it was signed on the dotted line was led so far down that garden path.

For me, if you spend your life reading and writing prose or code, text rendering quality is surely paramount. I’m curious what you think the energy should be spent on instead.

It’s way more fun to set a huge pile of VC money on fire.

Just in case anyone reads the parent and the takeaway is you can’t: you can still operate UniFi that way if you want to. The cloud connection and apps are optional.

Agreed. As to the world lived in: most people are so enthralled with money that any risk to earning more in the future is unacceptable to them, sadly. Companies then bank on that behaviour to help sweep things under the rug.

The mention of OLED is sideways to the network stuff, it just so happens the device he chose has an OLED screen.

The protocol is FreakWAN, so there’s no TCP/IP involved. LoRa devices send messages opportunistically and listen out for other messages they can understand and then maybe act on if they choose to. It’s about as simple as you can imagine.

Isn’t DW state-owned by Germany?

They use commodity LPDDR4X or LPDDR5 depending on SKU, for M1 and M2.

Do we know how he cheated in the in-person over the board games? That’s the most fascinating aspect of the story now.

One thing that struck me as I read through was that the computational cost for TLS 1.3 is so expensive that it becomes infeasible to run on the slower machines, resulting in timeouts and failed connections while setting them up.

Yet those old machines had full GUI OSes and performant apps and snappy interactivity in their day. Is the sheer amount of computation required to facilitate TLS 1.3 really more than what was needed to run entire interactive GUI operating systems of that era?

Kind of mind boggling if so.