Emory Dunn @emorydunn@emory.coffee

@elomatreb How do a favorite and boost this multiple times?
Related: how/ why do computers even work!?

I completely rebuilt the backend API for an application I've been working on and I'm really not up to basically rebuilding the entire application right now.

I think it might actually be less work to just make the iOS version instead of retrofitting the macOS version.

I think I know why the compiler is mad. Protocols can't be encoded/ decoded automatically because the complier can't know what the actual conforming object is.

The Swift compiler is at it again. Not so sure what to do about this one.

I've finally figured out how to implement this API!

He says for the fourth time in as many months.

Attempting to optimize AppleScript code really is Sisyphean.

Up-until-recenty status: https://xkcd.com/979/

Luckily I managed to find one whole person who had the same problem and they even provided an almost working solution.

I think if I'd plugged it in before I left wake for network access would work, but it looks like it's disabled when on battery power.

I've connected to my home network via VPN and can ping my laptop but I can't SSH into it.

I wonder if any of my roommates are home and could go and open the lid?

Nothing like discovering some files didn't sync up to the cloud before you closed your laptop.

How can Facebook screw up a simple chat text box so much? I can't even reliably type and delete text.

The key realization for me was deciding I don't need to create a full REST API. I only need to provide access to a limited set of URIs that map to methods which in turn call to AppleScript handlers that communicate with Capture One on the host system.

Once this is all in place the client side can be anything from a full instance of CaptureBot to an iOS Shortcut to a curl command.

After a bunch of back and forth with myself I'm finally beginning to get a handle on a (probably not the best) way to create the "server" side of CaptureBot.

The ability to interact with the host system remotely was always a key feature, but I'd never quite figured out how I wanted to do it. I think creating a strong server/ client model will provide the most flexibility going forward.

Someone submitted a pull request on a project of mine today. It's the first time I've ever been on the maintainer side and it's kind of amazing to know other people find my framework useful.

I came up with a great new idea for a project today and was really excited to get home and start prototyping it… until I realized I'd had the same idea nearly three years ago and actually wrote the underlying frameworks.

Now I'm really excited to scrap the old code and rewrite it with three extra years of coding experience 😁

I finally shipped a new internal tool that's replacing some Hazel rules I made to replace the previous version of the internal tool.