Micro.blog photo challenge π· Day 18: random (@JohnPhilpin)

Micro.blog photo challenge π· Day 18: random (@JohnPhilpin)
A dark and stormy night. Lightning everywhere.
Micro.blog photo challenge π· Day 17: hold (@dwalbert)
I love full moon nights where I can look outside and still see everything clearly. It’s an underrated benefit of having a life on Earth.
Micro.blog photo challenge π· Day 16: time (@rknightuk)
I’ve been a long-time user of Drafts, but my subscription is due to expire next month and I have been thinking that I’d let it go. I’ve been using Tot more these days, and Drafts had become an intimidating mess that I didn’t enjoy using.
However, after listening to a Mac Power Users podcast featuring the Drafts app and an interview with its developer, and then reading a blog post by Jason Burk about his Drafts setup (plus a personal conversation with him), I realised that it wasn’t necessarily Drafts that was the problem - it was what I had done to it.
That’s the thing, Drafts is almost endlessly customisable to enable it to fit different users and use cases. I had created so many Actions, Action Groups, and sections that the app had become confusing and overwhelming. I had duplicated actions across different groups, I was having to think too much whenever I wanted to use the app.
As I said to Jason, actual use beats good intentions. My Drafts configuration had become so bloated with convoluted actions that I thought I might use someday that it put me off from using the simple actions I will actually use today.
I’ve taken my myriad Action Groups and boiled them down to a single set. Now the only Actions that confront me are the ones I am likely to use and I don’t need to think about switching between different Action Groups.
I’ve also kept a couple of additional Action Groups but set them only as Action Bars - essentially an additional layer of text editing commands that sit at the bottom of my editing window. These are for formatting text, as opposed to taking action on them.
In terms of Workspaces, I’m keeping that as I previously had configured, but have clarified my thinking about them. I have workspaces dedicated to:
These are populated through smart searches based on a tag I apply to each note.
The Templates Workspace is specifically for OmniFocus project templates that I send to OmniFocus using the scripts that Rosemary Orchard created. I continue to use this system because it allows for date math (for example, a task will be deferred 6 months from the date the project is created).
I’m now feeling much more positive about Drafts after this cleanup. The Drafts editor is great, it supports all the Mac niceties (Services, smart markdown link insertion/pastes, etc.) and now I don’t feel overwhelmed when I load the app. Of course, Drafts also offers that great unique selling proposition of a blank field that is ready for text entry immediately. This is especially great on iOS.
Micro.blog photo challenge π· Day 15: clouds (@klandwehr)
After talking with @Burk I’ve been re-inspired with Drafts. I’ve streamlined my Actions to make the app more approachable. Actual use beats good intentions.
This Redbacks v Cougars game was a fun one to call. The game featured a bit of everything. I am loving doing NBL1 commentary this season!
Micro.blog photo challenge π· Day 14: fence (@val)
Micro.blog photo challenge π· Day 13: community (@crossingthethreshold)
Micro.blog photo challenge π· Day 12: tranquility (@vincent)
Micro.blog photo challenge π· Day 11: maroon (@rom)
Micro.blog photo challenge π· Day 10: pot (@warner)
We aim to keep Hemispheric Views podcast to around 45 minutes in length. We’re nailing it! Check out all the stats of the show π
This article was originally written for the December 2021 edition of Hemispheric News, delivered as part of the Hemispheric Views podcast member bonus program, One Prime Plus
Are you a Terminal wizard? A command line guru? A shell superstar? No, neither am I.
From time to time I attempt to teach myself. It never sticks. As a result I know just enough about the macOS (and Linux, I suppose) terminal (bash/zsh) as the faded memory of a series of beginner courses permit. Iβve resigned myself to this, and have found a happy medium of mostly using the GUI - but using the terminal for a few specific and useful things.
If you do nothing else with the terminal, itβs worth taking a look at homebrew(https://brew.sh/). Homebrew is a package manager for macOS. Put another way, it provides an easy way to install a whole bunch of Mac applications with a simple command.
To my mind, this is actually easier than finding the product website, downloading a .dmg file, dragging the application to /Applications, unmounting the .dmg and then putting it in the trash.
All of these steps can be replaced with the command brew install "appname"
where app name could be zoom
or microsoft-edge
or marta
. Brew then does all the hard work of grabbing the file and installing it in the appropriate location.
If you arenβt sure what the app is called, use brew search searchterm
. Itβs that easy.
Brew can update apps as well. Itβs a two-step process, with two commands:
brew update
to get the latest version information.brew upgrade
to perform an upgrade of all installed apps.Using the command brew list
I have checked out what Iβve got installed via brew at the moment.
Remember, Jason made me erase my iMac, so Iβm back to a short list at the moment, but highlights include:
As you can see, thatβs a mix of commercial and indie software.
Carrying on the theme, Brew has the concept of casks and formulae. All the apps above are casks - which eliminates the .dmg dance I described earlier.
Formulae are the instructions that tell a Homebrew what is needed to be downloaded to get a working app on your machine.
As a user, you donβt really need to worry too much about it.
Yes, itβs as safe as installing any other app on the internet. That is to say, the major apps will be fine. Microsoft Edge has had 32,214 installs via Homebrew in the last 30 days.
I believe there is a submission process for apps to be included in the homebrew directory, although donβt quote me on that. All the non-cask apps are open-source, so there is a degree of protection there in that you (or others) can read the code and identifying bugs or nasties if they so wish.
Iβve never had a problem, and I believe that Homebrew is just nerdy enough not to be an attractive vector for bad actors.
Micro.blog photo challenge π· Day 9: bloom (@thedimpause)
Micro.blog photo challenge π· Day 8: union (@odd)
Micro.blog photo challenge π· day 7: park @dejus
Micro.blog photo challenge π· day 6: silhouette @otaviocc