Curious what the methods you tried were 😉

I’m a big fan of the Chemex. Tends to be a bit brighter than the V60 IMHO. I also really like the Kalita Wave.

When I toured Ruby Coffee Roasters last fall, I asked Jared (who started the company) what his favorite was, he said this: nextlevelbrewer.com

I’ve got the original poster somewhere too 😊

You can view the original post (+ screenshots) here 👉🏼 practicalpkm.com/fixing-yaml...

After this, go to the Command Palette and run the Linter: Lint all files in vault command, and all your tags, aliases, and cssclasses will be updated to the correct format.

In the Linter settings, make sure the following options are configured correctly:

• Set the General → YAML tags section style to “multi-line”
• Toggle the YAML → Format YAML Array option on
• Toggle the YAML → Force key values to be multi-line arrays box add the cssclasses property

Changing this all by hand would be a major pain. Fortunately, it’s pretty easy with the help of the Linter plugin.

But first, make a backup of your Obsidian vault! You'll be changing a bunch of text files at once and there is no undo button.

The bottom line: all tags, aliases, and cssclasses properties must be converted from this:

tags: tag1, tag2, tag 3

to this:

tags:
- tag 1
- tag 2
- tag 3

Obsidian version 1.9 includes a couple of breaking changes:

1. The tag, alias, and cssclass properties can no longer be singular - they must be plural.
2. The values for these properties MUST be in a list. That means that all text-based properties are no longer recognized.

My overall takeaways from this incredible conference:

1. AI is disruptive, but not an existential threat to the creator economy.
2. The creators who thrive will be the ones who learn how to use it
3. Lean in to your humanity - scars and all.

⭐⭐⭐⭐⭐

And finally, Lestroundra Alfred taught us that consistency creates luck, so don't wait for it to come find you. Stop performing, start aligning, and discover that luck isn't random; it's strategic.