Public Relations

For this year’s Black Friday sale I held between November 27th and December 1st 2025, I pledged 30% of proceeds from app sales made on the Mac App Store and directly on my website to the Austrian St. Anna’s Children’s Cancer Research Institute.

The sale was a great success:
Because of your generous participation in the sale, we raised €766,43 for this cause.

❤️ From the bottom of my heart, thank you ❤️

Because it’s a larger sum than I had anticipated, I decided to:
1) Donate €100 to the St. Anna Children’s Hospital itself, for helping provide the best possible care for patients and their families. Amount already donated; proof available upon request
2) Donate €383,43 to the St. Anna Children’s Cancer Research Institute now. Amount already donated; proof available upon request
3) Donate the remaining amount (€283) to the St. Anna Children’s Cancer Research Institute in the new year. I’ll update this post once I’ve donated the amount

⚡️ Thank you again for helping fight cancer. And I do hope you’ll enjoy my apps!

💌 Contact & Connect

Read more

macOS 15 Sequoia introduced a new, annoying screen capture permission reminder that has brought on a lot of push-back from developers (myself included).

Now, Ricci Adams has found a way to virtually stop the nagging for specific apps. (I found out about this from Jeff Johnson’s Desolation of Blog blog).

First things first: Please use your own discretion when trying this. Consider if you’re savvy enough to work with the Terminal, and if you really want to remove the permission reminder for an app.

Apparently, there is a TCC (Transparency, Consent and Control) – protected file that keeps track of when to show the next nag screen for specific screen capturing apps, located at

~/Library/Group Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist

Using Terminal (which first needs to be granted Full Disk Access in System Settings > Privacy & Security), you can set that date far into the future so you won’t ever see the nag again.

For example, I wanted to make absolutely sure it never bothers me again for my own app ScreenFloat, so I just set it to my retirement date: January 1st, 4321.

defaults write ~/Library/Group\ Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist "/Applications/ScreenFloat.app/Contents/MacOS/ScreenFloat/" -date "4321-01-01 00:00:00 +0000"

Restart your Mac (or log out and back in) so it accepts the new defaults, and you’re all set.

Read more

Long story short, I done goofed: A bug snuck into my trial time code and ended it early for some users.
If you experienced this, please feel free to re-download the trial from the website (direct download here) for another, full 28-day trial.
My apologies for the inconvenience!

Links

ScreenFloat Website (+free, 28-day trial)
Get to know ScreenFloat 2 8-part Blog Post Series
ScreenFloat 2 Usage Tips

Purchase ScreenFloat on the Mac App Store
Purchase the Eternal Storms Software Productivity Bundle on the Mac App Store (includes ScreenFloat, Yoink and Transloader at ~25% off)

Read more

Just a quick note that since the betas (!) of macOS Ventura 13.0, configuration of 3rd-party widgets is broken, which, of course, means that Yoink’s widget’s configuration does currently not work, and I cannot do anything about it. Let’s hope Apple fixes it soon, macOS 13.0.1 didn’t bring any improvement in this regard.

Here’s a quick video of what I mean:

Again, in my testing, this not only was the case for Yoink’s widget, but a widespread issue over all sorts of 3rd-party widgets, although I do believe that dynamically app-supplied values work. It might only be static values that are affected by this.

At some point in iPadOS 16’s beta, this same bug occurred, but that was fixed before release. I guess the fix didn’t make it into macOS.
Maybe it’s time for another “Back to the Mac” event.

UPDATE (Dec 14th, 2022)

This is still an issue on macOS 13.1 (22C65). Quite embarrassing for Apple.

UPDATE (Jan 24th, 2023)

macOS 13.2 (22D49) seems to have finally fixed the issue – although it *did* take an initial

killall Notification\ Centre

to kickstart the widgets after adding and configuring them. But after that, it seems to work reliably.

Read more