benlivengood

My guess; server and consumer motherboards are very different. BMCs log a lot of data and on startup if the OS driver reads the log it can put whatever it wants in the crashdump. Consumer motherboards mostly only store the reason for last poweroff which the OS can read on next boot. Server MBs may also have a longer timeout before cutting power from a long-press.

Apparently from standby the power-off time on some laptops is much longer and you get a MANUALLY_INITIATED_POWER_BUTTON_HOLD which kicks off in the ~8 seconds from the article.

Instant gratification on rails, essentially.

On one hand you have slots/roulette/craps gambling where payout or loss is immediate. Next come candy crush style games where time invested per session is minimal but extant, but reward continues to stream with flashy graphics for accomplishing subgoals. Next come longer-term games like 4x or tower defence where there's progression or some sort (often available to skill or how much time you have to spend) where payoff is delayed to the end but there are still progress rewards like new technology or beating a wave of enemies. Finally RPGs and MMOs where there is (often) no final payout but leveling up, completing quests, acquiring special items, etc. happens at a pace that rewards time spent. At no time is the next step mysterious; there's a journal with next steps which will each provide their own rewards.

Contrast that with real life where reward is on a fixed schedule (N paychecks a month) with no short-term feedback on performance. At best a short "good work" reward fairly rarely from management. There are subtler rewards people get like socialization or status, but they aren't on a quest journal and they arrive less frequently for most people.

I think for extroverts in high social contact jobs it may actually be as rewarding as gaming, e.g. direct sales.

Contractors and spot workers (day laborers, etc.) also get a bit more frequent reward feedback, but far fewer rails unless it's a very canned pipeline of clients.

Contrast with the ancestral environment where hunting or gathering had minutes or hours between reward feedback and our natural senses and instincts provided a lot of the rails (hunger, visual attention to animals and edible plants, potential mates).

The question is where do you spend your trust. If you think that you'll always be able to find and patch 0-days before anyone else into the indefinite future then it's fine to defect.

If you want your customers to believe they won't be hung out to dry when the broader community patches before they can because you're no longer in the loop, you cooperate.

It's not like this is the last 0-day that will need to get patched and deployed in a hurry. "Not slower to patch than virtually anyone else" is a pretty sustainable place to be.

Hey, one of my university professors! GF2^8 is also great for RAID6+ and Reed Solomon codes.

Back in the day it was tractable to build AES lookup tables for computing MixColumns and SubBytes similar to the site's multiplication table. Then djb found a remote timing attack, so processors started implementing hardware AES instructions.

The article is literally full of "dogs" neurons and even more specific "boston terriers" and "terriers" neurons in the larger models.

Specifically, there were "lost property" and "honesty" neurons that drove the answer to return a lost wallet in Kimi K3.

That's the big news of this article, that concepts are finally becoming human-legible for many neurons in mechanistic interpretability.

What I envision is the ability to find the circuits and neurons evaluating morality and ethics and being able to figure out how they work at the boundaries and ensure safe deferral to human judgement or stopping outside of in-distribution behavior, which further is vetted against actual human values.

Last time I tried using Firefox on Linux with Keepass's passkey implementation it worked on the test page and a couple other sites but Facebook refused to add it, so I definitely believe that e.g. banks and various other important sites won't balk at restricting passkeys to Android, iOS/MacOS, and Windows. I am curious what other people's practical experience is with these kinds of sites.

Touche, DJB is one of the few people capable of writing secure C network code.

I also don't exclude the possibility of formally verified C code like seL4 having no RCEs, etc.

Golang also makes it possible to serve a web site or service from a single binary. You can even avoid linking libc if you stick to core Go (CGO_ENABLED=0), and it comes with all the http and tls libraries you need to replace the traditional web server (nginx, apache, httpd) as well.

I love C and wrote some CGIs in C in the past but I don't love concurrent programming in C. While forking and execing can use shared read-only mmap on .text segments, the .bss and .data will need initialization and copying; there's unavoidable startup overhead that a threaded process avoids, and raw pthreads is kind of painful. If all you need to do is serve a low traffic site, CGI is fine.

My biggest worry would be how often the SQLite DB gets backed up because there's no way a C web server will be free of RCEs in today's world.

On the other hand, if a proof exploits a bug in Lean then it's ~trivial to prove a contradiction, so you can just check all the proof steps to see if it also allows doing that.

Similarly if the formal Lean problem statements (human generated) are correct translations into Lean (and the original NL statements are sound, which one would hope after decades), and no Lean bugs are abused by the proof (as defined above), then the proof is valid.

The NL/Lean discrepancies are super annoying and will make human analysis hard and fraught, but as many posters have found out the models themselves will gladly pick apart the NL-Lean translation for errors, and so my guess is that finding the discrepancies will not take too long. OpenAI really should have done a dynamic workflow over every lemma and step to ensure pointwise accuracy in the translation.

Forgejo/Gitea are pretty easy to set up and compatible with GitHub Action syntax. PRs work almost identically. The mildly annoying part is that Kaniko got deprecated by Google and the company that forked and maintains it doesn't publish binaries so you'll have to build it from source yourself if you want isolated non-root builds in your runners. Any of the major LLMs will get it running pretty solidly without much trouble, though.

I combined it with Zot for an OCI registry but there are quite a few choices there.

I'm shocked it's not being renamed American Intelligence.

Similarly, I had the option to CPU-mine almost as much Bitcoin as I wanted in 2008 when I first read the whitepaper, but I didn't, so I guess I should write an article about how half of Satoshi's coins should be mine?

Nah, it's cumulative errors per claim. E.g. maybe the per-decision-factor rate is somewhere over 50% but overall most claims will have errors because so many factors go into coverage/reimbursement decisions.

So what you're saying is that we lack a reproduction study?

Great; let's design and fund a study of the development of artificial intelligence that's as causally divorced from the ~extropian days as possible and see what they come up with. Barring that:

Basically that is what we have up until the early development of transformers; I don't think the authors of early deep learning or transformers papers were part of the rationalist sphere. The rationalists famously didn't believe neural networks or deep learning could achieve anything close to AGI.

So there are several diverse traces of intellectual development leading to modern estimates of AI risk and they vary from low to high without a lot of correlation back to the school of thought they trace back to. This leads me to believe that overall we have fairly good coverage of cultural ways of thinking about AI and AI risk, and aside from a minority of holdouts (LeCun) they have high enough x-risk or catastrophe estimates to take it seriously (e.g. >1% over the next few decades).