tylerhall

Developer of the app here. You’re correct. Accessibility APIs + timer + transparent top-level NSWindow that ignores input and draws a border.

Indeed, I buried the lede in this post. But I wanted to have fun with such a silly idea, first.

Thanks, but that's not the port number :-) That was just for illustrative purposes.

Good sleuthing, but the missing port number is simpler than that. I just blacked it out of the screenshot. I know very well that running sshd on a non-standard port has no benefits security-wise, but it does lessen the length of my log files from dumb script kiddies. I redacted the port in the screenshot for that reason.

Yeah, it's a $5/month DigitalOcean box with only my blog on it and nothing else. All assets come off a CDN and Varnish is sitting in front of WP, but looks like that still wasn't enough this time. It worked fine for my previous two HN'ings earlier this year.

> it’s probably useful to others?

That's my intent. I'll put it back online for others to find once the fuss dies down.

Sadly, I mean it. Don't want to go through this again. Taking down the post for now.

Yeah, sorry. That's just Xcode's default header. Feel free to open a PR or issue.

OP here. I think we're aiming for the same thing - though with slightly different priorities.

Of your list of minimums that DefaultApp omits:

Not every app adheres to a Document-based pattern. The apps I personally build typically fall into a "shoebox" style where explicit documents aren't used.

And there are other data layers than CoreData, which is why I didn't add that - especially since even with CoreData everyone has their own favorite library/framework. So that's easy enough to drop-in for those who want it. (That said: probably 95% of the apps I write use CoreData, so )

A customized NSToolbar would be great, but, again, there are so many implementations out there, which one would you pick that would satisfy the majority of apps/developers?

Anyway, like the accompanying blog post says, this project is "highly opinionated". It's just what I've cobbled together over the years. I'm not going to die on a hill for any of my particular choices. Do what works best for you.

OP here. Thanks for pointing out that omission. It's MIT like all my other stuff. I've updated it.

OP here. I never installed Catalina (or any recent beta software in years) on my primary machine that I get work done on. My Catalina testing this Summer was explicitly kept to an old laptop and virtual machines.

My "simpler" comment was about my mistake in signing into iCloud on those test devices. I learned my lesson and either stayed logged out or used a test iCloud account for the rest of the Summer.

And, overall, my post and comments in general are about running Catalina now that it's publicly released. Not about issues I experienced as a beta user.

Been running WP for god knows how long for my personal site, while my company website is built with Jekyll.

In June I migrated to Ghost simply to try it and learn more about Node. It was _fine_, but never really fit my mental model of how a blog should operate or a web app should be structured. For better or worse, I'm an ex-Yahoo and a PHP guy through and through.

sigh I switched back to WordPress literally five days ago and haven't yet gotten around to installing a caching plugin. My bad. I've turned Cloudflare caching on in the meantime.

OP here. Thank you. I have no issues with the tightening of security and permissions on Catalina. In fact, I welcome it both for myself and my aging parents who I want to remain safe online. My issue, as you said, is the implementation and lack of documentation for those of us who do know what we're doing.