I posted that previous note with a link to a draft article in it mainly so it could be shown at the online HWC – but also it marks the point that I’m starting trying out working on draft articles ‘in public’. They are still tucked away in my wiki, so not really that public, but at least online somewhere in case (as sometimes happens) I never finish them – some of the nascent bits will at least still be there available to the world and possibly useful.
Working on a draft post about owning my event discovery and RSVPs:
commonplace.doubleloop.net/20200401181719-indie_events_and_rsvps
I’ll be attending and most likely working on a blog post that I need to write about owning my RSVPs, before I actually forget what I did at IWC London.
Alain Badiou saying that despite the current necessary state interventions, the pandemic will not by itself change anything politically. But he doesn’t really say what actually is required to do so, other than the left needing to work on ‘new figures of politics’. Not much to go on.
Mentioned on Tom Critchlow’s website tour was Venkatesh Rao’s ‘calculus of grit‘. (Gotta say, finding some of these terms for basically ‘doing stuff on your website’ a teensy bit overwrought… but fair play, naming concepts does give you something to refer to and discuss).
I’ve not read the full article yet, but sounds like it’s a way of tending to the garden of your wiki.
It boils down to:
- release work often
- reference your own thinking
- rework the same ideas again and again
I’m trying this out at the moment – putting thoughts in the stream, linking them back to ideas in the wiki, and updating those wiki pages as I go along. Going alright so far.
Reading Venkatesh Rao‘s article “A Text Renaissance“, and part of it is some interesting thoughts on Roam (“a note-taking tool for networked thought”). I stumbled across org-roam (emulating Roam in Emacs) recently, while looking for a way of improving my flow of working on my wiki, and am loving it so far.
Venkatesh says:
Roam attempts to implement a near-full conception of hypertext as originally conceived by visionaries like Vannevar Bush and Ted Nelson.
Returning to these ideas is exciting.
The text renaissance is an actual renaissance. It’s a story of history-inspired renewal in a very fundamental way: exciting recent developments are due in part to a new generation of young product visionaries circling back to the early history of digital text, rediscovering old, abandoned ideas, and reimagining the bleeding edge in terms of the unexplored adjacent possible of the 80s and 90s.
Roam is built on Clojure (a modern Lisp), so props there too. I’m unlikely to use it myself, as it’s a silo, but looking forward to working in this style.
While it’s useful to break down ideas into fine-grained units, collecting the dots, you have to connect them back together again to make sense of them. A collection of dots alone isn’t much use (although just navigating around them can be fun).
People often get carried away when they discover the original vision of hypertext, which involves a network of documents, portions of which are “transcluded” (included via hypertext) into one another. The implication is that readers could follow any reference and see the source material—and granted, this would be transformative. However, there’s a limit to the effectiveness of the knowledge network as a reading experience. “Hypertext books,” online books which are made up of an abundance of interlinked HTML pages, are mostly unpopular.
Reading CJ Eller’s quick thought on a community of gardens. The idea is that to a small degree we might be responsible for the upkeep of others’ sites, such that our digital gardens are not quite so fenced off from each other. It sounds like something more than simply commenting on others’ posts. It’s a nice phrase, kind of a form of networked learning.
The garden metaphor is a compelling vision for what a blog can be. It implies that our thoughts can grow over time with the right kind of nurturing care.
[…] But sometimes it feels as though these gardens are enclosed. Sure, a blog might allow comments, but this feels as though we are operating on a layer above the soil. Are others planting anything new, tending to the weeds in our garden, or are they talking to us from the fence that separates our garden from them?
Via a link to Jared Pereira’s personal website tours posted on the IndieWeb chat, I stumbled on a bit of a goldmine of thoughts on the blog and wiki combo over at Tom Critchlow’s blog.
Lots of interesting new terms:
- blogchain: a string of short, ad-hoc posts in a blog that together build on a theme.
- digital campfires: somewhere in between the stream and the garden? A place for conversations.
- stock and flow: another metaphor for the wiki and the blog, the garden and the stream.
- collecting the dots: a nice phrase for the ideas in building a second brain, zettelkasten, etc.
- blogging without a publish button: seems like a way of building up articles over time, in draft, in public on the stream and the wiki.
Also learned about are.na, which says it provides ‘tools for thinking, together‘. Which I like the sound of, but as are.na is a silo, it’s not something I will be using personally.