Brett Terpstra released a nice upgrade to Marked 2 yesterday with some improvements for Bear integration. I purchased my copy of Marked a couple of years ago through the App Store. To preview what I was writing in Bear in Marked was a bit tricky. I always wondered why. In fact, it took me a while to figure out how to do it. Well, Brett answers why it was tricky.
Before I start talking too much about Bear, there’s one issue to note. Bear writes its preview files out to a system temp folder that Marked can’t permanently access from the sandboxed Mac App Store version, so users are constantly asked for permission. If you’re using Bear with the Mac App Store version of Marked, I offer a free crossgrade to the unsandboxed direct version. If you use the Help->_Report an Issue_ feature and just send me the top part of the report section (above the
---), I’ll consider that enough proof to provide you with a license. You can also contact me through the support forum.
I took Brett up on his offer for the crossgrade to the unsandboxed version Marked. Now viewing what I’m writing in Bear in Marked works as it does in my other apps.
If you’re using the App Store version of Marked I suggest you also take Brett up on his offer. You’ll be glad you did especially if you use Bear.
You’ll want to delete the App Store version of Marked and then install the unsandboxed version.
There’s a Mac and iOS app update for Bear out today. I ran the update on my iPhone, iPad and iMac without a hitch. On my MacBook, the update wasn’t showing up in the Mac App Store Updates section on my MacBook. I knew it was available because as I already said I had run the update on my iMac.
In the old App Store, when you went to the Updates tab it would automatically look for all new updates. In the new App Store it appears to not do the same. Anyway, I closed the App Store and relaunched it, went to the Updates section and the Bear update still wasn’t there.
If this ever happens to you there’s a way to force the page to reload. Here’s what you do. Open the App Store > Updates > Store in the Menu Bar > click on Reload Page. After doing that my Bear update showed up.
It sounds like the successor to nvALT is finally on its way. According to Brett, it is codenamed nvUltra. The final name to be determined later.
You can sign up for the email list, and get notifications and beta access as it comes out by signing at the bottom of Brett’s post over on his website.
Codename: nvUltra – BrettTerpstra.com
You’ve been hearing from me for years about BitWriter, the nvALT replacement I was working on with David Halter. Well, I failed at my part, then we lost touch, and it never came to fruition. Now that my health is back to working state, I attempted to pick the project back up. Turned out David was MIA (hopefully ok), and the code I was left with no longer compiled on the latest operating systems. Seemed like it might be time to let go.
Then I heard from Fletcher Penney. You know, the guy who created MultiMarkdown, and who develops my favorite Markdown editor, MultiMarkdown Composer. He was working on a similar project and invited me to join him on it. Now we have an app nearing beta stage that’s better than any modal notes app you’ve used. Code name: nvUltra.
Apple is now offering data migration services for free when you purchase a new Mac or need to have a Mac replaced or repaired. Until now data migration was $99.
Tidbits heard about the policy change from a reader and confirmed the change with an Apple Store Operations Specialist.
Beginning April 2, there will be no cost for Data Migrations with the purchase of a new Mac or Data Transfers with a repair.
My iMac is a late 2013 non-retina model. That’s close to 6 years old but it still runs fine. The only problem has been that it’s still on Sierra.
I’ve been reluctant to upgrade it to Mojave for two reasons. One is I was afraid I would run into the same problems I had when trying to upgrade from Sierra to High Sierra. I wrote about it here. Two is a problem that I read about on several forums where after upgrading to Mojave fonts are blurry on non-retina Macs.
So, here’s what finally convinced me that I needed to bite the bullet and attempt to put Mojave on my iMac. A few days ago Agile Tortoise released a Mac version of Drafts. Drafts is an app that I use regularly on iOS so of course, I wanted to have it on my Mac as well. So off to the Mac App Store I go to get the app. Come to find out the Mac version requires macOS 10.13 or higher and I’m running 10.12. I need to update my macOS.
To make a long story short I upgrade my Mac to Mojave without a hitch. I didn’t notice any blurry fonts but a few articles suggested running this terminal command so I did.
Apple’s macOS Mojave disables subpixel antialiasing, also known as font smoothing, by default. On a MacBook Air or a desktop Mac hooked up to a non-Retina display, upgrading will make your fonts look worse.
Update: We’ve found a better method that will actually re-enable subpixel antialiasing rather than just relying on font smoothing. Open a Terminal and run the following command:
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO
Log out and log back in for your changes to take effect. Thanks to Dean Herbert for reporting this to us.
I now have Drafts on my Mac as well as the latest macOS.
The other day, I bought Moom after trying the free trial for about an hour. It’s an amazing Mac app for managing windows. As a side note, I’d tried it several times before but gave up on it because I found getting started confusing.
Before Moom, I was bouncing back a forth between Better Touch Tool and Magnet. I wasn’t really happy with either one and was looking for a replacement. This time around I was determined to understand how Moom works. So, after installing it I did a search for getting started with Moom. I came across this video Wrangle Your Windows with Moom by Kevin Yank that does a great job of explaining how to set up and use it.
If you’re looking for a way to manage windows on your Mac you ought to download the Moom trial and get started by watching Kevin Yank’s video. You’ll be glad you did.
I have been using Day One for going on three years now. One concern I’ve had is that journals by default are encrypted but with Day One holding the encryption key. This means that someone at Day One might be able to access my journals. Journals with Standard encryption are also exposed to a data breach or security glitch. This has caused me to limit what I write in them.
Now, after reading Shawn Blanc’s ”Best Journaling App for iPhone, iPad, and Mac” on The Sweet Setup I’ve taken his advice and enabled End-to-end encryption for all my journals.
End-to-end encryption is not turned on by default for providing the best type of security for your journal entries, as users must maintain their encryption key at all times to unlock journals if necessary. As Day One’s FAQ puts it:
When using end-to-end encryption, it is essential you save your encryption key in a secure location. If you lose your key, you will not be able to decrypt the journal data stored in the Day One Cloud. You’ll need to restore your data from an unencrypted locally-stored backup.
We recommend turning on end-to-end encryption whenever you create a new journal to ensure your data is always kept safe and secure. Save your encryption key in an app like 1Password or a locked note inside Notes.app and never lose the key.
Now no one has access to my journals without the encryption key. I keep it in 1Password.