In the past days I have been both exploring my process for second order note taking, and part of that is evaluating tools. I’ve been trying the note taking process in both WordPress and Evernote. In parallel I have also been looking at other tools for note taking. I’ve looked at a few tools that say to have implemented the Zettelkasten method, but I don’t want tools that assume to shape my process. I want to shape my tools, based on my routines.

In terms of tools that support me, I want tools that increase networked agency. Tools that treat data as fully mine, the tool itself as a view on the data, and its interface(s) as queries on that data.

Between WP and Evernote, the first does that, the second most definitely not. At the same time Evernote makes note taking much easier than WP can ever do. This is not surprising as WP is a blogging tool that I am using as a wiki on my local host while Evernote was designed for note taking. From the other tools I looked at, Joplin and Obsidian stood out, both tools that use markdown. Joplin because it is open source, allows easy import from Evernote, and can save webpages locally, can sync with Nextcloud allowing easy mobile access. It does store notes in a sqllite database which makes accessing my data more difficult.

Obsidian is still in beta but already looks pretty amazing to me (similar to Roam it seems). It operates on text files in a folder, thus allowing direct access through my file system to any data I add. It provides a view on that data that allows easy linking between notes, and you can split off any number of panes in the interface with whatever content or query. This means you can have a variety of notes open, pin them, see what links to what etc. There is also a graphical view, that allows you to explore notes based on the cloud of links they form. That makes it look a bit like the Brain of old. It’s all in markdown, so easy to use on mobile with a different client if I sync it through Nextcloud. I added the same notes I previously added to WP and EN in Obsidian, to experience differences and commonalities. In comparison with the other notes tools I tried a key difference is that I left this app open since I started it up this morning. A key difference with WP and EN is that I want to add notes to this tool. It does mean I need to relearn markdown, which has gone rusty since I last used markdown (in a locally hosted wiki), but of course it was easy to make a note and pin it to use as cheat sheet.

Obsidian screenshot, list and search pane on the left, a graphical overview middle top, a note middle bottom, and my markdown cheat sheet on the right

Having used Obsidian for a day, I am now wondering if I still need my local WP instance. The combination of Obsidian and Zotero which I started using for reading references even looks like something to replace Evernote with. This is the first time I’ve thought that in the past 4 years for longer than an hour.

I’ve been exploring my note taking, trying to shape it as a more deliberate practice. As part of that exploration I’ve been reading Sönke Ahrens ‘How to take smart notes’ on Luhmann‘s Zettelkasten (now digitised). More later on that book. What stands out in all things I find about note taking is the importance of taking time to process. Going through notes iteratively, at least once after you created them first.

My own main issue with a lot of the stuff I collect, is just that, it’s a collection. They’re not notes, so the collection mostly never gets used. Of course I also have a heap of written notes, from conversations, presentations I attended etc. There too a second step is missing, that of going through it to really digest it and lift the things out that are of interest to myself and taking note of that. Putting it into the context of the things I’m interested in. The thing I regularly do is marking elements in notes I took afterwards (e.g. marking them as an idea, an action, or something to blog), but that is not lifting them out of the original notes into a place and form where they might get re-used. Ahrens/Luhmann suggest to daily take time for a first step of processing rough notes (the thinking about the notes and capturing the results). Tiago Forte describes a process of progressive summarisation, every time you happen to go back to something you captured (often other’s content), for up to 4 iterations.

There are different steps to shape in such a process. There is how material gets collected / ends up in my inbox, and there’s the second stage of capturing things from it.
I started with looking at reading non-fiction books. With my new e-ink reader, it is easy to export any notes / markings I make in or alongside a book. Zotero is a good tool to capture bibliographic references, and allows me to add those exported notes easily. This covers the first step of getting material in a place I can process it.

The second step, creating notes based on me digesting my reading, I’m now experimenting which form that should take. There are several note apps that might be useful, but some assume too much about the usage process, which is a form of lock-in itself, or store it in a way that might create a hurdle further down the line. So, to get a feel for how I want to make those notes I am first doing it in tools I already use, to see how that feels in terms of low barrier to entry and low friction while doing it. Those two tools are a) Evernote (yes I know, I want to ditch Evernote, but using it now is a way of seeing what is process friction, what is tool friction), and b) my local WordPress instance, that basically works as a Wiki for me. I’m adding key board shortcuts using TextExpander to help easily adding structure to my notes. I’ll do that for a few days to be able to compare.

I made 7 note cards in the past 2 days, and as the number grows, it will get easier to build links between them, threading them, which is part of what I want to experience.

Nicholas Carr wrote a blog post well worth a read last January, positing the impact of social media is content collapse, not context collapse. Indeed when we all started out on social software the phrase context collapse was on our lips.

Since 2016 Carr sees context restoration however, a movement away from public FB posts to private accounts, chat groups, and places where content self-destructs after a while. In its place he sees a different collapse, that of content.

Context collapse remains an important conceptual lens, but what’s becoming clear now is that a very different kind of collapse — content collapse — will be the more consequential legacy of social media. Content collapse, as I define it, is the tendency of social media to blur traditional distinctions among once distinct types of information — distinctions of form, register, sense, and importance. As social media becomes the main conduit for information of all sorts — personal correspondence, news and opinion, entertainment, art, instruction, and on and on — it homogenizes that information as well as our responses to it.

Content collapse, because all those different types of information reach us in the exact same templated way, the endlessly scrolling timeline on our phone’s screen.
Carr posits our general unease with social media stems from this content collapse even, and names four aspects of it:

First, by leveling everything, social media also trivializes everything….

Second, as all information consolidates on social media, we respond to it using the same small set of tools the platforms provide for us. Our responses become homogenized, too….

Third, content collapse puts all types of information into direct competition….

Finally, content collapse consolidates power over information, and conversation, into the hands of the small number of companies that own the platforms and write the algorithms….

My first instinct is that it is that last aspect that causes the most unease. The first and third are ultimately the same thing, I feel. The second trivialises not the content but us. It severely limits people’s response range, leaving no room for nuance or complexity (which makes unease and lack of power more tangible to users, such that I suspect it significantly amps the outrage feedback loop in people’s attempts to break the homogeneity, to be seen, to be heard) It is what removes us as an independent entity, a political actor, a locus of agency, an active node in the network that is society.

So here’s to variety and messiness, the open web, the animated gifs of yesteryear, and refusing the endlessly scrolling algorithmic timelines.

Bookmarked The New Old Home (by The Yak Collective)

My motivation goes here

I need to much more closely read this report. It is very much connected to the things I tried to express during the 2010 SHiFT closing keynote, when I labelled it as MakerHouseholds. A label under which I have done various projects related to making and networked agency in the past decade. There’s a richness in perspective to explore, written by people, some of whom I already follow in my feedreader. (ht Alper Çugun)

Rediscovering the home as a production frontier

The Yak Collective’s second report, The New Old Home, offers 22 perspectives built around Pamela Hobart’s central thesis: as work returns to the home in the form of remote work opportunities (a trend now dramatically accelerated by pandemic circumstances), we can turn to historical modes of integrated living, reconsidered in light of newer technology, to guide our attempts at co-located life and work.

Quotebacks have been mentioned in various corners of the IndieWeb a lot in the past few weeks. As it was launched as a Chrome plugin, I didn’t try it out (Chrome is an unpalatable ad delivery vehicle imo). Now however there is a Firefox Quotebacks plugin, Tom Critchlow announced.

As Tom says, Quotebacks are meant to reduce friction in quoting other blogs/sites/sources, and if that increases the number and length of distributed conversations I’m all for it.

I think of it as smoothing some friction for behaviors we’re interested in encouraging

How is it different from a block-quote? It isn’t actually, under the hood it is still a block-quote. It’s just styled differently, and the browser plugin makes it very easy to capture everything you need and paste it into your blog-editor. The quoteback you see above is a html block-quote in the source:

screenshot of the html code of a block quote styled as quoteback

While reading you can select text and in Firefox press alt s, and the plugin will pop-up. It allows you to add / edit things, and then copy the html encoded quote to your clipboard, to paste into your blog editor.

screenshot of the Quoteback plugin pop-up during browsing

I like the easy ‘quote, copy, paste’ flow and having it look nice. I do think that the styling, which mimicks how e.g. Tweets are embedded in websites, may sometimes however actually break the flow of a blogpost, where a block-quote is more like a highlight in the pace and rhythm of a text, while a quoteback is presented as an embed, a different thing separate from the text. In fact I mostly actively dislike the embedded tweets in e.g. ‘news’ articles. There it feels like a way of not having to write an actual article or story, resulting in ‘news’ items along the basic template of “X said something, Twitter wasn’t having it” (With the article often stating the content of a tweet in its text, and then embedding the tweet below it, repeat 12 times. Voila, ‘journalism’ done.) It’s an additional visual amplification, easy on the eyes yes and instantly recognisable as a visual pointer to elsewhere, that probably isn’t always warranted, and may even reduce attention to the post the quote is used in. That would then decrease the level of distributed conversation, not increase it as intended.

Of course it is entirely possible to use the quoteback plugin, and not having the visual style of embedding applied. Below is the exact same quoteback as above, but with the class="quoteback" removed, reverting it back to a regular block-quotes (but keeping the link to the source and comments you may have added). Alternatively you can also delete the script element that provides the styling information for the quoteback. (I do exactly the same with Flickr embeds)

I think of it as smoothing some friction for behaviors we’re interested in encouraging

I’ll experiment for a while to see how it works for me in practice. I’ve put the script that styles the embed on my own domain, so I can also fiddle a bit with the styling if I want.

Mijn Open State Foundation collega Wilma Haan wordt per 1 september adjunct-hoofdredacteur bij de NOS. Het is een prachtige stap in haar staat van dienst in de journalistiek. Helaas is de consequentie wel dat Wilma daarmee haar huidige rol opgeeft als directeur van de Open State Foundation (waar ik bestuursvoorzitter ben sinds Wilma’s aantreden). Dat vind ik heel jammer, want we waren eigenlijk net lekker op dreef met elkaar. Zoals ze zelf zei kun je de timing van unieke kansen die voorbij komen zelf niet plannen. Vanuit de Open State Foundation zullen we snel een vacature openstellen voor een nieuwe directeur om de belangrijke missie van Open State Foundation voort te zetten met ons toffe team. Tot september werken Wilma, het bestuur en het team nauw samen om te zorgen dat een nieuwe directeur een vliegende start kan maken.