I'm giving Capacities a try as a possible Obsidian replacement
I downloaded Capacities previously, watched some videos, and read some documentation, but I never actually did anything with it. And now I have — created a few documents, which Capacities called “Objects.”
It feels like Capacities is Obsidian 2.0. It does less than Obsidian, but it seems to do all the things I want it to do and perhaps all the things most Obsidian users need. Capacities is not easy to figure out, but Obsidian seems to require programming skills to make the most of it, and Capacities does not require those kinds of skills.
In the past, when I’ve switched to new productivity software, I attempt to build an organizational system early on, but this time my rule is to wait until it’s hard for me to find something or do something, and then add the bare minimum organization to fix that problem. I’ve got a couple of dozen documents in Obsidian now; I’m not going to sit here and attempt to figure out a system that will scale up to hundreds or tens of thousands of documents.
I like Capacities. It seems to do all the things I do in Obsidian, but easier. Like moving from a command line to a GUI. On the downside, it uses a block editor. I do not like a block editor. We’ll see if I can adjust.
Question for those of you who are familiar with both applications: What do I need to know about changing my Obsidian methods and workflows to suit Capacities? I write research reports and articles, each requiring days or months to research and write.
ME: [Closes MacBook, looking guilty, as Julie enters room]
JULIE: “What were you looking at?”
ME: “Nothing! I was just sitting.”
JULIE:
ME: “I was looking at home repair tips!”
JULIE:
ME: “I was shopping for a gift for you!”
JULIE:
ME: “Fine! I admit it! I was looking at porn! Nasty, filthy, disgusting, kinky, perverted porn!”
JULIE: “Don’t give me that! You were looking at productivity videos on YouTube again!”
ME: [ashamed] “Yes. Yes I was.”
Something I saw while walking the dog: Neighbors set up this sprawling little toy village on the front lawn of a condo complex. There is a lot going on!

When I migrated from mastododon.social to Micro.blog yesterday, I thought I might set up a read-only Mastodon account for accounts I want to keep up with. Then I thought nah. Simplify. One fewer social platform.
Also, I’ve switched off automatically syndicating posts from Micro.blog to Tumblr. For the few posts I want in both places, I’ll just cut-and-paste ‘em there manually.
Simplifying!
I’m moving from Mastodon to Micro.blog
Another way to say that is I shut down my Mastodon account, which was @mitch@mastodon.social, and transferred everyone that followed that account to mitchw.blog, which is hosted on Micro.blog, and where I’ve been posting updates for about two years.
My reason for making the change is to reduce the number of services I’m on, simplify posting, and also because I just plain like Micro.blog (though it can also sometimes be frustrating).
If you’re reading this from Mastodon or another fediverse service, hopefully you didn’t notice the change until I told you I’d done it. The fediverse makes that kind of thing easy (when it works right).
The WordPress-WP Engine drama doesn’t look great for Matt Mullenweg and, by extension, the companies he controls, including WordPress.org, Wordpress.com and Automattic. It appears that Matt is extorting WP Engine and WP Engine did nothing to violate WordPress license — not even close.
The messy WordPress drama, explained — Emma Roth at The Verge.
If WordPress is to survive, Matt Mullenweg must be removed — Josh Collinsworth blog