The impact of the work is greater when you examine what one single new technology would do to existing society, as in Primer (2004), rather than "start on a society with severl new technologies", like in Star Wars.
The Google Story Chapter 21. A Virtual Library mentions that Paul Allen was interested in trying to create something like the "Final Encyclopedia" from this book. This is somewhat the same motivation for Google Books and Google's activities more broadly, as shown in their organise the world's information mission statement.
Charles Bukowski by Ciro Santilli 40 Updated 2025-07-16
Video 1.
Something for the touts
. Source.
We have everything and we have nothing
And some men do it in churches
And some men do it by tearing butterflies in half
and some men do it in Palm Springs
Laying it into butter-blondes with Cadillac souls
This stuck to Ciro's mind for some reason. His brain just keeps completing the sentence, over and over:
Ciro Santilli does it in his computers and in his labs!
Some key points that are a bit hard to grasp, at least in some versions:
  • How did Bill Haydon know Jim Prideaux was going to Prague if it appears to be organized as a closely guarded secret by Control?
    • the film suggests Prideaux must have told Haydon himself, his close friend, against Control's orders of secrecy, out of loyalty, and in order to protect his friend.
    • The series suggests it was a honeypot
    so which one is it?
  • How does Smiley deduce that the Witchcraft source, Merlin, is Poliakov? A key step is when top people at the Circus question him about Ricki Tarr, and appear to suggest that there is a link between Ricki Tarr and Merlin. And Ricki told Smiley that Poliakov as the link to the Mole. Smiley understands that it was Karla who tipped off London Center about Ricki's coming through Merlin. He also observers that Witchcraft gives ideological infiltration campaign intelligence after Ricki comes back, as a way to discredit Ricki. It is still all a bit indirect.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact