Creating Next-gen Digital Brains
Warning
After a few years of technical writing, I felt limitations in writing platforms that kept me from writing the best-class articles I wanted. Technological knowledge is dynamic and intertwined, and none of the current formats can best represent it, not academic papers, lecture videos, code examples, or straightforward posts. I examined some attempts that addressed this, stuff called the second brain or digital gardens, but none seemed to correctly solve the problem. So I distilled my inconveniences into this huge mega-post and imagined what I would've done if I had created the new incarnations of digital brains.
Update 2022-06-12
Since this post I have extensively studied non-linear PKM software, such as Roam, Obsidian, Logseq, and Foam. I acknowledge that I misunderstood the concept of manual linking. PKM software performs a fuzzy search to intelligently identify linked and unlinked references. I found some PKM software with automatic linking, such as Saga or Weavit, but none worked how I expected. Manual linking helps refine the database. So even if I make a Next-gen digital brain, I will not remove the linking process.
Update 2022-07-01
Well, you're now watching my next-gen digital brain! For the past two weeks, I have worked on the WWW project that built this website. It checks off almost all of the marks detailed in this post!
TL;DR
- Create an aesthetic-interactive-automatic pile of code-image-repo-text that organizes-presents-pitches itself.
- There is no manual tagging, linking, or image processing, etc., etc.
- You just throw a random knowledge, creating a knowledge mesh network.
- The algorithm operates everything. It will be contained, processed, organized, and distributed all around the world in different languages.
- You don't tend knowledge. The algorithm penalizes outdated content (you can mark the post as evergreen to avoid this.)
So what's the issue?
Apart from popular belief, I noticed the best method for managing a digital garden is not tending it. Try to make a digital jungle instead. You don't take care of it, nature will automatically raise it.
The digital brain should make as little friction as possible.
The less you tend, the more you write.
Especially,
I despise the [[keyword]] pattern prevalent in so-called second brains (obsidian, dendron, ...).
Not to mention it performs poorly for non-alphabetical documents,
it is manual - creates a lot of friction.
The fact that you must explicitly wrap them with brackets doesn't make sense... What if you realize you want to make a linkage to a term you've been writing for 200 posts?
Do you go back and link them all one by one?
No! The solution must lie in algorithmic keyword extraction.
Organizing Contents
Interconnected entities
Practical knowledge doesn't live in simple posts, though posts might be straightforward. Create a knowledge bundle that interconnects a GitHub Repository, Codes, GitHub README, and other posts in the same brain network.
Look at Victor's post, with rich metadata for the paper, dataset, demo, and post. That's what I mean by interconnected entities.
Interactive Contents & Animations

Unorganized Graphing.
Trust me, manually fiddling with tag sucks.
Necessarily tagging posts and organizing posts into subdirectories resembles organizing your computer.
You wouldn't want to do this if you have thousands of posts, and the border gets loose too. What if the post has two properties? What becomes the primary tag and what becomes the secondary tag?
Notable trends. Gen Z's don't organize folders anymore!
Recent trends, I would say, are dumping everything into a mega folder and searching up things whenever needed.
I also used to organize folders a lot more, but recently, as searches like Spotlight and Alfred improve, I don't see the need to manage them all by hand, considering I always pull up those search commands to open a file.
You don't need to manually organize all of the files when algorithms can read all the texts and organize them for you!
Use algorithmic inspections to analyze how the posts may interrelate with each other properly.

So create a cluster of posts, not classified by me, but by bots and algorithms.
WordPress also has this plugin.
This is similar to backlinking, which most so-called digital brains like Obsidian and Dendron do.

I agree with the importance of interlinking knowledge crumbs, but I can't entirely agree with their method.
Manually linking posts is inconsistent and troublesome. It can only be done on a massive communal scale, like Wikipedia.
You cannot apply the same logic to individual digital brain systems.
SEO and Open Graphs
Precis Bots for Meta description
I can apply the above technique for crosslinking to TL;DR bots for meta tag descriptions.
Automatic Open Graph Image Insertion
For example, GitHub creates automatic open graph images with their metadata.

Quite a few services use this technique.
GitHub wrote an excellent post on implementing this feature.
I also tried implementing this on top of Ghost CMS, then gave up after figuring out Ghost Core Engine should support this. But I made a fork I can extend later. http://og-image.cho.sh/
GitHub - anaclumos/cho-sh-og-image: Open Graph Image as a Service - generate cards for Twitter, Facebook, Slack, etc (project note)
Multilanguage
Proper multilanguage support
Automatic Langauge Detection. The baseline is to reduce the workload. I write random things, and the algorithm will automatically organize corresponding data.
hreflang tags and HTTP content negotiations. I found no service that uses this trick properly, outside megacorporate i18n products.
Translations
At this point, I might write one English post and let Google Translate do the heavy lifting.
Also, I can get contributions from GitHub.
While supporting multilanguage and translations, I want to put some 3D WebGL globe graphics. Remember infrastructure.aws in 2019? It used to show an awesome 3D graphic of AWS's global network. AWS Edge Cloud Continuum
I kind of want this back too. Meanwhile, this looks nice:
Also made some contributions...
Fonts and Emoji
I want to go with the standard SF Pro series with a powerful new font Pretendard.
However, I am exploring other options.
I liked TossFace's (site) bold attempt to infuse Korean values into the Japan-based emoji system for emoji. (lol, but they canceled it.)

Honestly, I want this back. They can use Unicode Private Use Area. But Toss is too lazy to do that considering they still didn't make the WOFF version Webfont.
So I might use Twemoji.
Domains and Routes
URL Structures
Does URL structure matter for SEO? I don't think so, as long as the exhaustive domain list is provided through sitemap.xml.
For SEO, though I still doubt the effectiveness, automatically putting the URLified title at the end might help, like Notion does.
Nameless routes
Autolinks with alphanumeric IDs | GitHub Changelog
I don't like naming routes like cho.sh/blog/how-to-make-apple-music-clone. What if I need to update the title and want to update the URL Structure?
Changing the URL structure affects SEO, so I would need to stick to the original domain even after changing the entity title to maintain the SEO. But then the title and URL would be inconsistent.
So I would give the entity a UID that would be a hash for each interconnected entity. Maybe the randomized hash UID could be a color hex that could be the theme color for the entity?
Emoji routes seem cool, aye? I would also need Web Share API since Chrome doesn't support copying Unicode URLs.
Some candidates I am thinking of:
- cho.sh/♥/e5732f/ko
- cho.sh/🧠/e5732f/en

Miscellany
Headline for Outdated Posts
There should be a method to penalize old posts. They should exist in the database but wouldn't appear as much on the data chain. Put a lifespan or "valid until" for posts.


Footnotes
An excellent addition. But not necessary.
If I ever have to make a footnote system, I want to make it hoverable, which namu.wiki did a great job. I do not want to make it jump down to the bottom and put a cringy ↩️ icon to link back.
ToC
A nice addition. But not necessary.
Comments
Will go with Giscus.