Bell's theorem by Ciro Santilli 37 Updated 2025-07-16
Basically a precise statement of "quantum entanglement is spooky".
Sun Wukong by Ciro Santilli 37 Updated 2025-07-16
Only after Ciro became an adult did he finally understand that Sun Wukong was the basis for Dragon Ball as mentioned at: Figure "19th century illustration of the Journey to the West protagonist Sun Wukong". And that Sun Wukong was a million times more famous overall. Mind blown.
His given name "Wukong" literally means "the one who mastered the void" (Wu = Comprehend, Kong = void), so clearly a Dharma name. Edit: it is actually given in the novel, he was born without name. They seem to be Taoist however.
The family name sun1 孙 is the same character as "grandson", but most educated Chinese people seem to be able to recognize it as a reference to "monkey" from some archaic context not anymore in current usage.
Figure 1.
19th century illustration of Sun Wukong
. Source. TODO check that it is actually 19th century. Because en.wikipedia.org/wiki/File:Xiyou2.PNG for Zhu Bajie, obviously from the same print, says it is 15th centure.
Figure 2.
20 Sun Wukong depiction in Peking opera
. Source.
Insider trading can discourage investment, and cause CEOs to hide information from employees. While there have been arguments that insider trading makes share prices more quickly go to their proper value, the true solution is that if investors dislike insider trading, companies can legally declare that they will only work with those that legally agree not to trade its shares or facilitate insider trading. If someone unaffiliated with the company simply overhears or comes across insider information, this won't stop them, but even if it were illegal, it would be nearly impossible to prove such a case.
At first glance, it would seem pretty ironic for an FAQ that lambasts intellectual property rights to place restrictions on its own distribution, even if just attribution. But asking for attribution is consistent with libertarianism.
It is to prevent people passing this FAQ off as their own work, as they could get social/monetary benefits from doing so, and that should be considered fraud. Even if they don't explicitly claim to be the author when using its contents, that is likely to be assumed by most readers, so not explicitly disclaiming it should be treated as fraud.
This does not mean that anyone who doesn't provide attribution must be sued into oblivion; the punishment must be proportional to the crime, after all, and in most cases, any personal clout gained from omitting attribution will be negligible. But for the very few cases where it's not, the license facilitates the prosecution of such fraud in the current legal system.

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