Show newer

I think I'm on a three-week publishing streak with blog posts now. Hopefully I can keep up this pace.

This week in my weekly journal, I touch on my personal knowledge base, a little Terraform, and the Elasticsearch licensing fiasco.

Here's a taste of what can happen to businesses who put all their tech eggs in one proprietary corporate basket: Moral of the story: don't do it.

The year of the Linux desktop has come and gone (I think it was around 2014) and we have missed it because we assumed it meant Microsoft losing. Sadly, it probably means we also have failed to gain the freedoms we sought.

These past few weeks it sure seems like 2021 took a look at 2020 and said, "Hold my beer.".

While I'm not doing the full thing, I am trying to be a bit more diligent in updating my blog this year. To that end, I'm working on writing a weekly review of interesting things I work on.

The coming wave of digital regulation may claim to target “Big Tech” but will inevitably end up harming citizen-innovators most because regulators have forgotten to include them in their process.

(My input to Open Forum Europe's pre-
@fosdem #EUOpenSource)

Sightly bummed that there really isn't a FOSS alternative to OneNote and Excel. While tools like Libre Office Calc and Joplin are pretty good one their own, they're not really equivalent.

How to spot the rights-ratchet business model before the project switches to a closed license (and blames the issue on everything but their strategy).

I've been procrastinating for a long time, but this might finally be the year where I (mostly) de-Google myself.

I guess it's safe to say Firefox is dead now that Google is intentionally knee-capping Chromium.

Unpopular opinion: 

There is no "good guy" in this latest dust-up between AWS and Elasticsearch. Both companies are behaving terribly, and in this case I think Elasticsearch is the worse of the two.

AWS should be giving back to the open source projects they leverage, and there is no excuse for not doing so.

Elasticsearch co-opted an existing open source project, Lucene, and now are trying to make it proprietary. They want others to contribute to the project, while keeping all the money.

I wonder if a zettelkasten is a good place to keep higher-level documents like how-tos and cheatsheets? Maybe I'm trying to force a square peg into a round hole?

Show thread

Hmm. After sleeping on it, I'm beginning to think my problems with updating my zettelkasten have less to do with the method and more to do with how I take notes.

I need to get better at distilling what I read down to a few core ideas that then get recorded in my permanent notes.

But I do like the idea of keeping everything in git as markdown documents. Maybe I need to rethink how I'm approaching things.

Show thread

Sometimes I wonder if it's worth the effort. I'm not a writer, and ultimately what I want is more of a personal knowledge base. A place to keep my notes, cheatsheets, guides, and other documents.

Show thread

Some days I think I like the idea of having a zettelkasten more than putting in the effort to actually have one.

Whoops. Just realized I still had a Keybase proof listed on my profile, even though I deleted that account when they were acquired by Zoom.

Not that going back to Twitter is something I've seriously considered.

Show thread

Looks like somebody has registered a new Twitter account using my old username. Guess there is no going back now.

Show older

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.