The next generation of information management

Some 15 years ago, I was enjoying Journler. The thing I really liked about it back then was, it could post an entry straight to Blogger. Of course, Google likes to screw around with Blogger. They broke the posting mechanism that Journler used, and now they’re concentrating on keeping it deliberately broken for Safari users. Over the years, Journler slowly sunk into the morass of apps that got left behind by advances in MacOS.  I continued to use it to capture flash fiction, scenes, and chunks of longer stories, until it became unusable. The source code for Journler has been available on Github for a long time, but I just now found out about it.

But I digress. As Journler wheezed and died, I tried a variety of paper and app systems to capture stuff I wanted to come back to later. Evernote was okay, until they crippled the free version to support only two devices (previously five). Google Keep held my interest for a long time; but I’m trying to extricate myself as much as possible from Google these days—and if I could find something better that isn’t WordPress, I’d go through the hassle of moving everything. Perhaps my longest-running attempt has been using Tines to keep notes and to-do lists organized. And yet, I’m always keeping my nose in the air, sniffing for a better way of doing things.

Recently, I started looking at journaling apps. Day One came highly recommended, and had the huge advantage of both Mac and iOS apps that talked to each other. I gave it as honest a chance as I could—downloading both the MacOS and iOS apps—and even with the daily prompt on my phone, I never really warmed up to it.

Someone suggested Logseq last week, and it sounded interesting enough to give it a try. The developers describe it as “a privacy-first, open source knowledge base,” and the videos they link to from the home page (an enthusiastic user who describes how to make the most of it) convinced me to give it a try. It can run either as a webapp, writing to your hard drive, or as a standalone desktop app. The developer says he was heavily influenced by Roam Research, Org Mode (Logseq supports Org Mode, although it defaults to Markdown), Tiddlywiki, and Workflowy.

The interface looks invitingly plain, at first. You’re presented with a journal page with today’s date on it, but otherwise blank. Start typing, and it supports Markdown (a big plus)… oh, wait. It’s also an outliner (and given my long-term relationship with Tines, that’s another big plus). Oh, type two square brackets and enter a title, like a Wiki link, and you get a new page that you can click to enter (yeah, I’ve always been fond of Wikis). Oh, type /TODO Download the desktop app on a line, and you get a to-do entry. Put hashtags on entries you think you’ll need to come back to later.

Clusters show groups of related entries

This seems like a chaotic way of doing things… until you display the graph. Then, Logseq gathers up all those scattered to-do entries, those hashtagged items, and other things, and pulls them all together. Some call this a digital garden or digital knowledge garden—me, I just call it software magic. Of course, you get out what you put in. You can create custom queries to pull things together based on how you want them. If you leave it running overnight, click the little “paw print” icon at the top left to open the new day’s journal page. Maybe this is what makes Logseq so much more approachable for me.

It took me a day or two to realize that this is the most natural approach for working with Logseq. There’s a lot of layers to it, and this brief post isn’t doing it justice. I’m using it at home with the desktop app, and at work using the webapp (because Doze complained about how not safe the desktop app was). Either approach works fine.

There’s a mobile app called Obsidian that can be set up to work with Logseq’s files, but it’s a private beta right now and I don’t need it just yet.

Now I have to figure out how to pour all the different entries in all the different paper and pixel systems I’ve accumulated over the years into Logseq. Someone wrote a script to convert Google Keep to Markdown, so that’s settled. I hope I can write a script to pull all my old Journler entries in.

Resurrecting an old dirt bike (part 1)

Mason's latest obsession (the bi-weekly obsessions have mellowed into bi-monthly) is getting a dirt bike. We still have the one we got for The Boy; it has been (mostly) sitting under a tarp for a couple decades. Saturday, we dragged it into the driveway and got started.

1978 Yamaha DT100E… and Mason, who blinked at the wrong moment. (The seat is also flipped up.)

I'm not sure why it was put up in the first place, but we’ll give it a good shot to get running again. Despite it being 43 years old, and thrashed pretty thoroughly before The Boy got hold of it, I think we can do it. After all, I’m even older, and have been thrashed around a lot, but I’m still going. After the initial blush of enthusiasm, Mason realized it was going to require some work to get this thing going, and started grousing about getting a new one. After a few rounds of “this is what you’ve got to work with,” he came around. A co-worker graciously offered to gift him some safety gear! (I have mixed feelings about my current employer… I have many issues, but they have taken an intelligent approach to the pandemic and my co-workers totally rawk.)

So, we got started. The gas tank was filled with rust and sludge, and the carb was a mess—white powdery stuff dried up inside, and the choke and idle adjust frozen. (I would have thought I’d have known to drain the fuel out of the dang thing.) The cables were frozen. None of the above are show-stoppers—a week’s soak in Simple Green fixes most carb problems, gas tanks can be cleaned out by pouring a handful of screws in it and shaking, and I have a cable lubing tool.

We got an impressive amount of crud out of the tank. I’m not sure it’s done just yet, but we should be down to details now. De-crud’ing a gas tank is a matter of pouring in a handful of small hardware (screws, nuts, etc.) and shaking. We started with some gas in it on Saturday, got sludge out, let it dry yesterday, then put the screws back in for more shaking. Blowing compressed air in blasts out an impressive amount of stuff, the majority of it dust but some sand-sized particles as well. Once the particles are no longer an issue, I’ll probably get some liner to seal off further rust.

The throttle was frozen to the handlebar, it turned out—once I got it off, we applied a wire wheel and file to the handlebar until the rust was no longer binding the throttle sleeve. A little cable lube sprayed down the top of the clutch and brake cables got them cooperating.

The carb is at Travis's place (he works on most of the farm stuff); when we brought some parts to fix the Kubota SUV/golf cart, I told him about the project and he offered us the use of his whizbang carb cleaner—it uses sonic waves to do in a couple hours what soaking in Simple Green does in a week. We'll have the carb back tomorrow. In the meantime, we need to get new grips, an air filter, probably new tires (maybe later). Lube and adjust the chain. There’s an off-road place in the next town up, and we at least got grips today. Mason also wants brush guards, which isn’t a bad idea, but we’ll get it running first.

While I was working on the important stuff, Mason decided to hit it with some spray paint. The back fender is now silver. The bike was originally orange, and a previous owner painted it Yamaha Blue. I’ve had to repeatedly remind Mason that, if you want to do it right, you have to take the bike pretty much entirely apart to paint it. Well, I would probably have wanted to paint it first thing when I was 11. Aging sucks, but it does bring a little perspective along with it. Meanwhile, Charlie wanted to apply wrenches to it, and Mason went off the rails (as he often does when Charlie wants to get in on the action).

If we do get it running, it will be kind of interesting to see how things pan out. He has wondered out loud if it’s too big, and has talked about wanting to do wheelies and stoppies (the latter is when you grab enough front brake to loft the back tire). The answer to that is, “maybe.” He’ll have to learn to work a manual clutch, a skill that will serve him will if he inherits the Miata. Back in The Boy’s day, I put a larger rear sprocket on it to slow down the top end (I pitched it to The Boy as “it’s easier to do wheelies”)… although I think it will hit 50MPH with a little running room as is.

I can see him tailing the Kubota, while we work on the fence, and maybe he'll ride the fence line and let us know about issues (before the cows get loose again). We can always hope he’ll use his power(sports) for good.