Byzantine fault

Mm-hmm

... all these computer science, uh, you know, researches and, and, and discoveries and the, and the solving of the, uh, Byzantine General Problem, et cetera, right? Like, so Bitcoin is working, but at the same time, it's also a proof of concept just in general for this idea, I would say.

And I just, I just love that because in a sense, Bitcoin is this physical thing, this, this manifestation in the physical way, you know, with the miners and the energy and the computers-

Right

In 1982, three computer scientists at SRI International in California, Leslie Lamport, Robert Shostak, and Marshall Pease, published a paper proving exactly this.

Their paper gave us the Byzantine generals problem and a family of solutions for tolerating it, what we now broadly call Byzantine fault tolerance, or BFT.

And their solution, when you hear it, is almost insultingly simple.

Ready? To fix the system, you add one more participant, Charlie.

It aims to provide a starting point for understanding how distributed systems evolved and highlight influential research papers across decades.

In the comments, the community mostly discussed the importance of Lamport's work and his influence on distributed systems.

Users debated the readability of Lamport's papers, with some finding his writings less accessible, while others appreciated their clarity.

There was considerable discussion about the relevance of classical papers like Paxos and Byzantine fault tolerance, and whether newer approaches have replaced them.

The blog post announced the open sourcing of dbt charts, a declarative language using YML for creating dashboards and charts through chat agents.

It explained how current AI tools generate complex files that are hard to audit and improve, and proposed dbt charts as a middle ground, enabling charts to be defined in code with SQL, YML, Markdown, and Jinja.

The article highlighted the advantages of using a structured declarative language for transparency, maintainability and integration with dbt along with a hosted platform for collaborative analytics all designed to support ai driven and code-based workflows in the comments the community largely supported the launch emphasizing the importance of unbundling bi reproducibility and open standards Many recognized dbt charts as a promising step toward replacing traditional proprietary dashboards with code-based, auditable, and shareable artifacts.

There was debate about the choice of YAML as a language, with some arguing it limits flexibility, while others appreciated its clarity for version control and auditing.