Little technologies in this site

Some examples of the freedom of self-hosting, and the low-hanging fruit in all nonfiction:

• Metadata. YAML. Lets me build indices of the best posts, most important topics, and a timeline.
  • Content notes. I don’t want to distress anyone who doesn’t want to be distressed.
  • Topic imporance.
  • Quality. IMO.
  • Epistemic status. Marking each post with the confidence level or literalness, genre. Originator.
  • Argument. The thinking person’s TL;DR.
  • Last page edit. Nice for emphasising that the content is changing.
    
    

• Information hiding. bigfoot and JQuery Accordions.

• Bug bounties. To keep me honest.

• Server magic: Jekyll and Ruby. Can do anything. Text deduplication, link reuse, quote database, etc.

• Feed. I actually initally forgot about good old RSS, because it is so easy and so reliable that it fades into the background of life, and ceases to appear as technology.

• Anonymous feedback. Unauthenticated Google Form.

• Disclaimers. Most book reviews are by people unfit to judge their truth, including mine.

• Psychology. What am I like? What sort of person writes this?

• Opinions. I used to dream of listing all of my premises. This is both impossible and too much work, so instead I list some things I think you should know.

• Worldview message digest. Quotations database.

• Licence. Licensed under Creative Commons Sharealike.

• Style consistency. SASS (meta CSS)

• Static comments. Netlify Forms. (Staticman is cool but brittle.)

• Typesetting maths. MathJax.

• Data analysis transparency. Github ipynb viewer.

• Diagrams. matcha.io

• Memorial. GNU

• Tables. https://www.tablesgenerator.com/

To implement

• Rotproofing my links. Gwern’s archiver.
• Internet Archive option for all links. Or auto replace script.
• Maybe make content notes more prominent.
• GRADE evidence quality scale?
• Time since modified vs error discovery rate