silkqin.com by Ciro Santilli 40 Updated 2025-07-16
John Thompson's Guqin website.
Holy crap amazing list of Guqin pieces by the guy for MP3 download! www.silkqin.com/06hear.htm And the explanations are insane. What a dude. Ciro Santilli's hero.
Download all MP3:
wget -r -np -l 1 -A mp3 http://www.silkqin.com/06hear.htm
Ciro Santilli Contacted John by email in 2019 telling him to put his stuff on YouTube and offering help, and he replied, but nothing came of it unfortunately. Edit: he uploaded a bunch of videos of him playing live in 2020! www.youtube.com/user/silkqin/videos
John focuses on playing the tunes in a "historically informed performance", in particular using silk strings rather than metal ones which are used by most modern artists: www.silkqin.com/08anal/hip.htm
Video 1.
Dialog between Fisherman and Woodcutter performed by John Thompson (2020)
Source.
Ubuntu by Ciro Santilli 40 Updated 2025-07-16
Ciro Santilli's Linux distro of choice as of 2019.
It ain't perfect, but it's decent enough.
The greatest advantage of it being that it has the likely largest desktop user base, and therefore the highest likelihood that your problems are solved on Ask Ubuntu, and goes together with Ciro's philosophy that "people should do everything in the same way to factor stuff out", especially the open source losers.
Ciro considers that the killer flaw of Ubuntu, and most desktop distros of 2020, is that no one under the Sun knows how to build them fully from source: Linux distribution buildable from source. This is why Ciro based the Linux Kernel Module Cheat on Buildroot, see also: Linux distribution buildable from source.
韦编三绝 is a chengyu that means "to study diligently", i.e. to read so much to the point that your book starts to wear down.
There is a Chinese Wiki page for this song: zh.wikipedia.org/wiki/韦编三绝 which says it dates from the early Qing dynasty
Video 1.
"The book binding broke three times" uploaded by guqincn
. Source.
Lit: fish timber question answer.
The dialog is also known as allegory for an incredibly deep philosophical discussion between an idealized wise woodcutter and a fisherman, e.g. mentioned at: www2.kenyon.edu/Depts/Religion/Fac/Adler/Writings/Fisherman%20and%20Woodcutter.pdf
This song is just too slow for Ciro Santilli to make much out of it.
Figure 1.
Dialog between Fisherman and Woodcutter Chinese traditional painting by Xie Shichen
.
Video 2.
Dialog between Fisherman and Woodcutter performed by Wu Jinglüe
. Source. Accompagnied by di flute to reinforce the idea of two voices. This one has TODO year.
On Ubuntu 23.10, a crash led to the creation of:
/var/crash/_usr_bin_gnome-shell.1000.crash
After that simply running apport-cli as:
apport-cli gnome-shell
led to the creation of: bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049368 a bug on the gnome-shell package.
Their crash system does not have an amazing user interface.
Tested on Ubuntu 21.10.
After something crashes, look under /var/crash for a crash file, which helps to determine which package to report under on Launchpad.
E.g. a file /var/crash/_usr_sbin_gdm3.0.crash makes you want to file the bug under gdm at: bugs.launchpad.net/ubuntu/+source/gdm/+filebug
Then, while reporting the bug, you want to give the developpers access to that .crash file. But you can't publicly upload it because it contains memory dumps and could contain secret information. The way to do it is to look at the ID under:
sudo cat /var/crash/_usr_sbin_gdm3.0.uploaded
Ubuntu's crash report system has already uploaded the .crash for you, so you just have to confirm it and give the ID on the ticket.
You can view a list of all your uploaded errors at:
xdg-open https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie/whoopsie-id)
and each of those contain a link to:
https://errors.ubuntu.com/oops/<.uloaded error id>
which you yourself cannot see.
Running:
sudo apport-unpack /var/crash/_usr_sbin_gdm3.0.crash /tmp/app
splits it up into a few files, but does not make any major improvements.
apport-retrace
sudo apt install apport-retrace
sudo chmod 666 /var/crash/_usr_sbin_gdm3.0.crash
apport-retrace -g /var/crash/_usr_sbin_gdm3.0.crash
opens GDB with the core dump. Debug symbols are supplied as separate packages, which is a really cool idea: so you should be able to download them after the crash to see symbols. askubuntu.com/questions/487222/how-to-install-debug-symbols-for-installed-packages mentions how to install them. Official docs at: wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages
Tried:
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list
echo -e "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse\ndeb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list
sudo apt install ubuntu-dbgsym-keyring
but then sudo apt update fails with:
E: The repository 'http://ddebs.ubuntu.com impish-security Release' does not have a Release file.
ScopeFun by Ciro Santilli 40 Updated 2025-07-16
899 USD as of 2022, takes a year to ship as they gather up a lot of orders before producing.
Sounds so cool, especially the multi functionality. Shame so expensive.
"Ibis redibis nunquam per bella peribis" is a Latin phrase that translates to "You will go, you will return; you will never die through war." This phrase is part of a longer poem known as "Ibis," attributed to the Roman poet Ovid. The work is characterized by its exploration of themes such as fate, death, and revenge, often invoking mythical references and a sense of foresight.
The "Most Vexing Parse" is a term used in C++ to describe an ambiguity that arises in the language when the compiler encounters certain declarations. It specifically refers to the situation where an expression can be interpreted in more than one way, leading to confusion about the intent of the programmer. One common example occurs when a function is declared with a certain syntax that can be interpreted either as a function declaration or as an object of a type being instantiated.
"Chomsky's Universal Grammar: An Introduction" typically refers to the foundational concepts and theories presented by Noam Chomsky regarding the innate structures and principles that underlie the grammar of all human languages. Chomsky introduced the idea of Universal Grammar (UG) in the 1960s, suggesting that the ability to acquire language is hardwired into the brain, and that all languages share a common structural basis.

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