This site runs best with JavaScript enabled.

A Short History of Bi-Directional Links

Last tended on May 16, 2020
🌱 Evergreen

With the recent rise of Roam Research, the idea of bi-directional linking is having a bit of a moment.

We're all very used to the mono-directional link the World Wide Web is built around. They act as one-way pointers we follow in a linear sequence.

While we can link to any site, the destination page hasn't a clue we've done so.

We set up all these single direction paths, trying to signal relevance and context, only to have the other side completely ignore our efforts.

Our monolinks are trying to establish relationships in vain.

We're starting to look around our mono-linked environment, and wonder why it's so hard to surface relevant, contextual relationships.

Manually interlinking content takes an awful lot of human curation and effort. Effort we should probably slog off onto our systems.

✶ Enter the bi-directional link ✶

A bi-directional link has social awareness - it knows about other pages or 'nodes' that point to it, and can make them visible to people. This means we get a two-way conversation flowing between our web locations.

Our fabled bi-directional link is not new.

This concept goes all the way back to 1945, when Vannevar Bush dreamed up the Memex machine.

Vannevar outlined this hypothetical gadget in the essay As We May Think – a system capable of "associative indexing... whereby any item may be caused at will to select immediately and automatically another... [so that] numerous items have been thus joined together to form a trail."

Vannevar even created a small informative diagram of this desk-bound vision. Marketing chops 101.

Vannevar had a fairly impressive imagination, especially given that digital computers had only come into existence 5 years earlier. Most were still the domain of large military operations like Bletchley Park, and seen as inconveniently large calculators.

Implementing a wildly interactive computational personal knowledge base wasn't much of an option.

So the idea went into hiberation, and didn't resurface until personal computing began blooming in the early sixties. Ted Nelson took inspiration from Vannevar's ideas in 1965 when he coined the term hypertext to describe his vision for a sprawling network of interlinking text.

Nelson planned to implement these hypertextual dreams in his perpetually-imminent Project Xanadu. If you have some time, this is quite the internet history rabbit hole to run down.
Ted Nelson is on another level.

The Xanadu system imagined that every sentence, block, and page would be part of a vast bi-directionally linked network:

Suffice to say, Xanadu didn't pan out.

Instead we got the less fancy, but far more real and useable World Wide Web that currently does not support bi-directionals on an infrastructre level.

While Sir Tim Berner's Lee wrote himself a note debating their pros and cons back in 1999, there is an obvious design issue with letting two-way connections flow freely around the web.

If every site that linked to yours was visible on your page, and you had no control over who could and couldn't link to you, it is not hard to imagine the Trollish implications...

Figuring out how we might filter, moderate, and set permissions around link visibility turned into quite the challenge. The design details grew complex.

It became clear implementing the Web with simpler mono-directional links was the right thing to do, given that its creators wanted universal adoption. Lots of people are still mad about it. Let's not venture too far down that historical wormhole.

The TLDR is technology is hard.

Until Xanadu ships and we're all immersed in the universe of multi-linked, version-controlled nodes of remixable micro-content (that somehow solves the problems of permissions and moderation), there are still plenty of ways we can resurrect the possibility of bi-directional links on the web...

A good starting place is our personal internet homes. Specifically, internet homes with experimental digital gardens attached

There's been a flurry of interest around bi-directionals among my fellow digital gardeners, originally sparked by Andy Matuschak's notes

Go have a good browse through these

There's plenty to admire here.It should be noted Andy is an experienced developer and interaction designer, and these notes should not be taken as the standard expectation for the rest of us normal plebby internet citizens. But the key part of this system that creates interlinked context is the "Links to this Note" section at the bottom of each post.

Anytime Andy links to another one of their notes on the site, it'll pop up as a related note here. This is the bi-directional dream.

It gives us a way to navigate through these ideas in exploratory mode, rather than navigating a hierarchy of categories on a main index page.

Since it's all contained within a single-author site, our Spammish-Troll-risk factor is at a comfortable zero.

That's all very cool, but how am I supposed to build this?

Thankfully, setting up your own public gardening bi-directional Memex doesn't involve Xanadu.

One fantastic option for non-developers is based around a personal wiki system called TiddlyWiki. Anne-Laure Le Cunff wrote up an easy-to-follow guide to getting your own up and running.

For those of us here for the hyper-customised, over-engineered Javascript solution (that would be me 🙌), the Gatsby.js community has a number of active gardening enthusiasts building themes and plugins.

I'll personally be implementing it using Aengus McMillin's gatsby-theme-brain and be livestreaming the process on May 19th.

You can read more details about that on Bringing Bi-Directional Links to Gatsby Gardens

This is mildly tangential, but I love how the topic of bi-directional links makes fully visible our "websites are locations" and "websites are containers" conceptual metaphors with "inside" and "outside" links.
Want to share?

Join the newsletter

For weekly notes on visual thinking, ethical technology, and cultural anthropology.

Maggie Appleton © 2020