Where should I keep notes?

I’ve been banging my head against a problem for a while and it is wearing me out, so I am gonna kick it out to you fine folks for advice.

My problem is that I want to keep notes in a searchable (digital) format, but I can’t figure out where or how. I’ve considered keeping notes here in WordPress, running MediaWiki or DokuWiki, just a bunch text files in git, a git-backed wiki, a wiki attached to a git repo, in one of a dozen Markdown enabled quasi-wikae, and so forth.

My past was my future

I learn by doing, and I remember through repetition. I have difficulty listening to what others say, so I take notes. I can hardly transcribe someone spelling a word or a phone number, because I just can’t keep all the immediate information in mind.

In the past I’ve been embarrassed about that, but I know there are both learning methods at work as well as my personal trauma that lends itself to my inability to listen to a person dumping information. I don’t judge myself so hard because I am an attentive listener to people sharing and emoting with me, and in an emergency I keep a cool head and can process information very quickly. It is that last fact that causes me trouble; I idle in emergency mode, hence my need to take notes when there isn’t danger.

Another thing about me that makes note-taking so valuable is that I attended 22 educational institutions before being kicked out of high school and passing the California High School Proficiency Exam. Between leaving school and taking the exam I worked in the IT department of a city government. In other words, despite the years of self-doubt and fear that I was a fool, I survived by becoming an autodidact early in life, and was more than prepared for the wellspring of knowledge that accompanied the ubiquity of the open web starting in the late 90s.

In other words, I learn by taking notes, and find inspiration in sharing with others.

Buckets and scaffolding

Recently I’ve taken the craft of note-taking and self-learning to new personal highs, and that means plunging into what I refer to as brain stuff. Everywhere I look there are explanations for why humans act as they do (that includes me), and it is a great body of knowledge that isn’t fitting into my existing framework of collecting information in deep buckets, and then mixing it across broad subjects or themes. And then of course repeating this over and over as I get more information, building the scaffolding of my knowledge until it becomes applicable.

Practically that means I am filling up notebooks and storing them, not fully processing the contents, and therefore capturing but not digesting. And it is wearing me down.

So I am looking for something, some system, that can relieve the pressure of my mind, a release valve to dump information somewhere I know I can find it later and move it around and draw conclusions and build into new self-discoveries, etc.


This isn’t the first time I’ve been thinking in wiki, and a lot of what I thought then still applies, except I don’t think the age of my tools (WordPress for example) are holding them back; indeed free software that is useful, and therefore used, seems to adjust and grow in the ways it needs to survive.

And if I am allowed a moment of romantic thinking, that method of survival appeals to me. ^_^

But that doesn’t solve my problem. Where should I keep my notes?

Words words words

Here are some things I would like, for sure:

  • Easy to write, which probably means Markdown for me, because I hardly use any formatting except for the very simple rules that are in all Markdown flavors (rarely headings, unordered lists a lot, and links are slightly easier than a hrefs).
  • Easy tagging, because I want to create ad-hoc collections of knowledge unintentionally
  • Easy referencing: double square brackets in wikicode is one of the most addictive properties I’ve ever encountered on the open web, it is my personal Xanadu.
  • Easy to search (not a huge problem, since my notes are just a complex index for my brain)

There is another category with one item in it, and I will call this “the thing I don’t understand about myself”: I want it to be publicly available. I am straddling a fence with this, because I don’t know what drives me to make everything that I produce public and open. I sometimes wonder if I deny myself a safe and private space to make mistakes and test assumptions without it being captured and used against me, but I feel I get enough of that from my family and friends, and that I can’t self-correct without the input and visibility gained from sharing publicly. Even if I decide on text files in a local folder, it will be synced somewhere public.

Okay, so those are my desires and a big question. Now consider the systems and tools I know.


Let’s start with the obvious, since this dance I have with MediaWiki is constant. A lot of the issues I have with MediaWiki, such as user accounts and spam won’t be a problem for my single user requirement.

There is so much going for MediaWiki.

  • Easy referencing, with reporting tools that assist in deepening buckets of knowledge (show me most referred to non-existent pages from a given category, please!)
  • Robust taxonomies and semantic tools for structuring data in personally meaningful ways, but still easy to tweak as needed
  • Decent search with additional options
  • PHP app, easy to use with my most familiar software stacks
  • Transclusion. Makes templating amazingly straightforward, and cross-referencing can be wondrous.

But there is still a lot about MediaWiki I can’t stand.

  • Installation really sucks for anything besides a vanilla install, dependency gets weird for something like the semantic modules.
  • URLs make me so irritated. MediaWiki is the only software I’ve come across that don’t form lowercase, dashed words in URLs. My name doesn’t start with M, and it visually distracts me when I view an article on a MediaWiki site. Workarounds break some linking functionality.
  • Themes in MediaWiki suck. There is a design aesthetic to wikae dictated by Wikipedia, and we might just be stuck with it. Alternatives ask that content be changed in such a way that one can’t easily switch between skins, and that is even worst.
  • MediaWiki markup is way more complicated than Markdown to do normal things, and alternatives require additional server resources I don’t want to give. So Parsoid is out for me.
  • Portability is an issue. I can’t copy and paste into a blog post, which is how it should work.
  • It seems kinda overkill to run such a robust framework for a single person to take notes.


Now here is a fun little project that hits a lot of my points.

  • New(ish) Markdown plugin that doesn’t require special tags to use.
  • Content is just text files with some extras around it.
  • URLs are sane, a direct comparison to MediaWiki.
  • Can do fun things with git, some potential for hacking there.
  • Very little hosting requirements.

Not many things I dislike.

  • Themes are kinda ugly, would need to fix that.
  • Searching is somewhat limited, and not many options to change, but could be a non-point with a decent taxonomy.
  • Taxonomies aren’t as easy to use.

Gollum (or any git-based file system)

Gollum is the wiki engine that powers GitHub, but more importantly to me, it is also used in GitLab. I am jumping straight to it, because it encompasses all the features of a regular directory of text files, but does a better job on various points.

  • Git-based, text files, very simple and efficient.
  • Easy to use with other workflows.
  • Markdown with smart extras.
  • Can be edited via web or text file.

But some features completely missing.

  • No taxonomies outside of folder structures, goes against emergence of patterns and cross-referencing I enjoy.
  • Links are not as easy to pull off.
  • Search is kinda dependent on larger system, which is iffy at best.

There is one thing that using a self-hosted git repo has that is very interesting: task management. The ability to track some thoughts as tasks that can be sorted, labeled, commented on and closed is very appealing, and will probably be used in note-taking regardless; closeness of tools in that capacity are a benefit.


Finally, WordPress. My career is more or less based on WordPress, so here are the advantages of using it for note-taking and sharing.

  • I’ve got Markdown (this very post is written in it).
  • I love the way taxonomies work in WordPress.
  • I’ve got a lot of options for search, due to my work providing hosting for very large WordPress sites.
  • I theme in my sleep (it’s a problem), so I can make the content look however I want, no lock-in.
  • It is very public, and I already plan on publishing updates in blog posts for insights I come upon, so it is already part of the process.
  • URLs are robust and sane.

On the other hand…

WordPress feels like publishing to me. This is silly, I know, so please comment on this: I want my notes to be found and feedback submitted, but I don’t want to present my unfinished thoughts as something worthy of being in my primary publishing pipeline (or 3P as I am calling it starting now).

I am already coming up with reasons that I shouldn’t care about this. Am I so concerned with SEO that I would go against my authentic self and try to separate a half-formed idea or preliminary research from how folks perceive me on the web?

What if I am walling myself into this single project, and everything looks like a nail to my WordPress hammer? Is the novelty of WordPress gone for me? Am I searching for a reason to use a different tool because I don’t think WordPress can handle it, or because I just want to try something else?

At the end of the day people work with me because they know me, or know someone else that knows me. I benefit greatly from presenting who I am upfront, so any fear I have around showing these other parts of myself doesn’t appear justified.

Wrapping it up

Okay, so I feel a bit better. Despite kinda processing that and realizing I am compounding my distraction by avoiding the tool I am most comfortable with, I’d still like to here your thoughts on this. Did I miss anything, or misunderstand how something works? Because I would love to know there is a specialized tool out there to do this thing for me.

And finally, what is a blog? It isn’t like I would type up shorthand notes, so anything I write will be legible to at least myself for future reference. Should I just blog my notes and categorize them as such? If I typed up fifty pages in one day, would that seem like spam, or is there an argument that such diligence in record-keeping is beneficial in this era of 140 character half-thoughts? Can a blog serve as externalized memory, while still providing useful information to others?

If you have answers, let me know. ^_^

Social Documentation

A long a convoluted series of thought-trains crashed together to give me this idea for a series of sites that I am now working on. It is mostly written in a notebook, but the gist of it is something I call “social documentation”.

It derives from me taking a step back and thinking about what I actually use non-Wikipedia wikae for, and how it is used by others. There are patterns in most wikae software that I like, but as implemented I can’t fit on other patterns that I would like. While I was thinking about this I was also considering how I would write documentation for my increasingly large and diverse client base.

I have a recipe in mind: WordPress + BuddyPress + bbPress + a custom theme + some plugins.

In the past I’ve been dismissive of BuddyPress because I didn’t use those patterns, and critical of bbPress because that software didn’t work the way I expected. Both projects have matured, and my understand of custom post types and the things that can be done with themes and plugins has grown. Now I think I can work with those frameworks.

And of course I am going to make it really complicated, by running my network of networks with multiple instances of social doc sites, which will share logins but have distinct communities (if I may presume that at least one other person will join me…). So there is that. ^_^

The first site that I will (well, should) focus on will be my work support documentation. That is straightforward in that it is easy to imagine what it looks like. If you’ve ever used a site that was titled a “knowledge base”, there you have it, though I endeavor to make it less boring and more helpful than most kb sites I’ve used.

After that, though, documentation changes into something for which I use wikae: aggregate logs of role-playing game sessions, notes and tutorials for video games, deconstructions and commentary on cultural artifacts (me talking about a show I just watched), comprehensive reviews on computing devices, and food recipes. Those are all real examples of what I plan to build, each a different site using a similar format, but distinct enough to power its own groups of users.

Most ideas I have don’t have as much visual/typographical design involved, so I am not practiced in explaining it. But in time it will become clear, because I practice radical transparency, and I will also be looking for suggestions and design patterns to take.

That’s all for now. Stay tuned. ^_^

Locking down the wiki

I thought about it for a day, and decided to set the wiki to only be editable by those with a confirmed email address. The main reason is that I don’t have time to fight spam now, and this may help. It isn’t a permanent decision, though I fear that I may just leave it like that out of frustration.

Eventually I hope to find a different method for combating spam, and if I went ahead with my plans for a wikae cluster and filled it with active communities, it might work. I’ve got to think about this, but I don’t have the energy to do so now.


AbuseFilter: First edit warning

I notice that a large majority of the bots that publish articles to the wiki only post once. I bet that most of them aren’t equipped to deal with additional pages in the workflow, so I made a very simple new filter. All it does is check if an account has ever edited before:

user_editcount = 0

Then it just pops up a message that says, “Hi! I am glad you are editing the wiki. We pop up this message the first time someone edits the wiki, to throw off the spambots. But you, precious human, should just submit again and we will let ya on your way! ^_^”

So far it seems to be doing a good job so far. ^_^

Thinking in wiki

I’ve been really into wikae lately, as is apparent by how much I written about it. A wiki is a particular set of features and workflows, and it has its own mindset.

I am thinking in wiki.

This site is becoming more of a journal, where my posts are either about flash in the pan events, or part of longer thought out articulations. The frequency of posts has gone down, because I am doing more mind-mapping in other places, like text files in git repos, and in various wikae.

It has brought a few things to light for me, about how I write, and what I am trying to create. Here are a few examples:

  • Temporality – A lot of the things (most?) I blog about are not important to me after a few months. That means I have old announcement posts and tons of broken links that have no value, but I keep them to provide temporal context. I am not convinced it is that useful.
  • Anti/Social – I think blogging is very important, but it does bother me that blogs are essentially silos. This isn’t really a critique, just that instead of loading up blogs with like buttons and allowing people to leave comments with their social network credentials, it is probably more worthwhile for the majority of bloggers to assess what collaboration looks like for them.
  • Our tools are aging – The software that runs some of the most important spaces on the web, like MediaWiki and WordPress, were developed a long time ago. It is easy to find feature requests from years ago, still being pleaded for. Again, not a critique, just an observation of what popularity does to software, and how dominance affects the culture and motives of the community that supports it.

These aren’t new, obviously. It is just me glancing at the gap between two software projects/workflows (WordPress/blogging and MediaWiki/wiki). Then I think about StatusNet, and how it looks like it could be practically abandoned for other projects. In one sense, that is a bummer, and I’ve invested a lot of time in it. On the other hand, maybe it isn’t so bad for things to get torn down and built back up, especially considering the transient nature of status updates, almost all of which are unimportant to me a few days afterward.

I’ve really pushed MediaWiki hard in the last couple of months. I’ve bumped up against a lot of walls, and some of them stopped me. But overall, I am happy with the result, which is a system to collaborate with those that want to, and a relatively decent way to create bodies of useful content. I am rushing as fast as I can to configure all the extensions I think I will need, so I can eventually just focus on creating. That will be the real test.