All you need is links
subconscious.substack.com
subconscious.substack.com
Here the idea is not so much 'links are you all need' as transclusion is all you need, in the form of dynamic popups/popins.
How can we have a ridiculous number of references? Make each one popup its metadata like an abstract. How can we have a ridiculous number of WP links for every term and concept? Pop them up, WP has an API. How can we cross-reference sections or arbitrary <div>/<span>s within a page? Make it popup. How can we cross-reference other pages without the dreaded hypermedia effect of "oh my god each page is 1 sentence long and I have to click through a thousand of them, screw you man"? Pop up with a mouse hover, effortless and fully recursive. How do we support backlinks, or indeed any arbitrary kind of metadata page about a link we may wish to create at some point? Just generate the HTML snippets and link to those snippets - popups do the rest. How do we implement tags? You'd better believe it involves simply creating a HTML page with all of the links with the 'tag' and then simply linking to it! How do we do topic-modeling with the coldstart problem of requiring heavy manual curation of all links (which is what OP suggests as a replacement)? Use topic-modeling to generate link suggestions while editing, and then link the useful ones (thereby making them visible when you edit and also generating backlinks automatically). When we can pop up anything, we can pop up raw data files like PDFs, or their syntax-highlighted versions (source code); we can even pop up pages on other domains (subject to a whitelist of having checked that X-FRAME headers don't kill it and it doesn't otherwise break horribly inside the iframe).
But if they didn't need to click. That would rock!
(I'm not sure what you mean by 'sidenotes'; what we call sidenotes are just footnotes, which are of course at the bottom of the document and don't need to be 'loaded'.)
Said is going to try to rewrite the spinner to cover the full rendering. I have also been thinking that for links to pages, like /Lorem (rather than links to a specific section of a page, like '/Lorem#images'), the total load time may be too bad an experience and it's time to go back to creating annotations out of the page abstracts, and then having the full page popup if necessary. (I was going to do something like this anyway in order to get my essays fully integrated into the tag/link-bibliography & similar-links systems, but I was going to keep the popups as live popups; now I probably won't.)
Popups are modal and nested popups represent a path of navigation. Accidentally move the mouse too much and everything disappears - and if the stack was deep, good luck trying to get it back, because you lose the entire path. There's no back button or undo close tab to rescue you.
So it's not actually frictionless, it actually induces mental stress the deeper in the navigation path I go. And knowing that I'd feel stress makes me not want to look at the popups at all, for fear that I find something interesting and feel that stress with a nested navigation.
I think it's an interesting experiment but it's not for me.
That's another problem with these: they swallow my browser history.
It's the opposite effect of experiments like the one on graph.global, which instead trashes the browser history (and breaks the back button).
Crusader Kings 3, a recent strategy game, implemented nested popovers like this to handle the same issue and now I wish every popover system had it.
Here's a demo for anyone curious: https://www.youtube.com/watch?v=Dg-WelHEsEU
This is an interesting attempt to reduce a problem space, but ultimately I think it ignores a lot of factors either in play where they see success or likely to cause it to falter should such reductionism be pursued. And in evidence is another major use case cited: attempts to replace hierarchical file structures have not been successful, because those hierarchies are meaningful for people who use them. This isn’t for lack of trying! Even the accompanying screenshot shows the detritus of that effort, just noise in the sidebar.
Assume you have your filesystem as a set of HTTP links, and you have tagging, and whatever else. How do you tell the difference between a link to a file and a link to a tag? It seems like you'd need to impose an additional structure, or type system, on top of just links.
I wanted to see that because as I read on I honestly had more problems understanding the concept and wanted to see the idea implemented so that I might understand. But nope :(
Does this make sense to anyone? This reads to me like GPT-3 wrote it, a simulacrum of a deep thought...
Yes, although it could be stated more clearly. The “pages that don’t exist” are conceptually a virtual page for each tag that links to every page that includes said tag. This is pretty obvious to anyone with some experience with contemporary note taking apps since they generate backlink pages dynamically.
the right way to say this is, "a tag is a special kind of page", which is far more boring (like.. didn't del.icio.us do this years ago?), but way more understandable.
In fact most of this article could be summed up as: most interfaces can be represented as a page of links.
This is what I did for my site.
Erm...that's exactly what a folder aka. directory in a filesystem already is:
https://en.wikipedia.org/wiki/Directory_(computing)
In computing, a directory is a file system cataloging structure which contains
references to other computer files, and possibly other directories.
Directories don't contain files or subdirectories, they just reference or "link to" them.There is no revelation in seeing that everything in the entirety of existence, physically or conceptually is built out of related stuff. Nothing exists outside of everything else, except a parallel universe maybe, everything is derived from something.
This is a major revelation, as it's not people's naive intuition. It's the basis of modern physics and category theory, the foundations of mathematic theories of the real and abstract worlds.
Either way, why use "links" as the analogy, why not just call them relationships? That's what they are. We know what relationships are just as well as we know what links are so no need to pick a familiar concept and extrapolate.
For possibly the majority of the planet, relationships between things do not jump out like an interconnected web and therefore that’s not their “fundamental truth of how the world is made up”. If that’s surprising to anyone else who reads this: welcome to the club.
Things themselves do not exist outside of conceptual thinking. Unless we can get down to the true atomic source of everything, then maybe you've found the distinct "thing", but you cannot experience that, only describe it.
For example, my "body" is made up of the ultimate fundamental atomic unit just like everything around it. There is no line of delineation, it's just a sea of atomic units. My body only exists as a distinct "thing" because that's how we interpret this sea of units with our limited senses.
I see it a little like pixels on a display. The array of pixels all display light, they are all the same, but as we zoom out we begin to interpret the many pixels forming distinct objects on the screen. This does not change the fundamental reality that the pixels are not that thing, and that thing does not exist outside of our interpretation.
And all of this is assuming reality is fundamentally atomic, which has yet to be proven.
In fact, it’s my opinion that it’s possible there is no Absolute Truth at all (if there’s any I suspect it might be math, but that’s way above my pay grade as it were) and that everything is simultaneously one, nebulous, and subjective.
However, for convenience we need to have these discussions about interconnectedness somewhere closer to the “We are humans interacting with a solid world” paradigm.
I thought the article made a lot of sense in that context, having also struggled in past with organizing notes: nested folders vs flat structure, longer 'document' notes vs short blocks, tagging, inter-linking, discoverability...
* Look at problem space
* Recognize it has a graph structure
* Graph structures can be modeled with links
The last step seems unnecessary, or at least it can be generalized/implied after recognizing the graph structure.
The really difficult part seems to be: Combining all of the ideas. Distinguishing between the types of links seems to increase the complexity again, but using links as a general model gets more interesting (to me) if it actually ends up in a unified space.
I believe there's a problem where people try to resolve everything with a single theory.
We need to been able to query our information base, and queries do need sometimes to offer more than mere full-text search. For that from tags to topic modeling many kind of meta-information are needed. They are hard, since automate them is hard, but they give back results that doing otherwise can't be equally reached so...
All models are wrong, but
dome models are useful.
George Box.
That’s my take on the article…it’s trying to be useful. Whether it succeeds is another matter.But to me there’s some potential merit in the radical conceptual reduction.
Merit in thinking about the simplest thing that might work.
What's unique about pagerank is that the next best improvement that will give you as much benefits would be way more complex. So yeah its simplicity is its main merit.
You can create notes within other notes with backlinks, you can tag notes and importantly, you can have dynamic blocks that access the note metadata like the outlinks and inlinks... Once I got comfortable with the dynamic blocks, I realised that I didn't need to tag my notes, I could just create links to topics and I found that approach to have some nice benefits. For instance, I started creating recipes and tagging them "Breakfast", "Quick", and I could then create a "Breakfast" note that displayed all the notes linked to it and had more control over what was being shown and write information around it.
This is basically what I do in Obsidian with the Zootelkeeper and Folder Note plugins. Every folder has a note attached to it with an autogenerated index of all the notes contained within. So for all my notes I use a hybrid of folders, indexes, and the graph view to navigate though everything. So far I'm not really needing to go more than 3 folders deep, mostly it's just 2 folders deep.
It reminds me of Stephen Wolfram's hunt for the base "structureless structure" — the hypergraph.
I was trying to find a way to make app data interoperable, tired of migrating notes between apps and losing data — this is how I'd do it.
I think it's almost impossible though (technically possible, just not economically viable).
If I had tons of money to burn on a pet project, this would be a dream place to spend it.