Long response times

[dv0d]

Hello,

since MacOS Sequoia (or the version before) and the required changes needed that turned into v 2.1.1, I noticed that response times are way higher than in older versions. It was super snappy and translation happened almost instantly, not it takes a good 5-10 seconds before translation is visible. Have there been changes to the API by dict.cc, or is there any other reason for it?
It's by far the most used workflow (or even app) I use on a daily basis, but due to increased loading times, it's annoying sometimes and I wish it would still be snappier.

Keep up the great work on this essential piece of software!

[dennis-tra]

Hi @dv0d, glad to hear that the workflow is valuable to you and thanks for your kind words!

I'm also using it plenty of times a day and it's still super snappy for me. In the past, I observed something similar where there was a delay introduced due to Apple's Gatekeeper/notarization service. Basically, Apple checks the hash of the contained binary against their servers for known malicious software upon invocation which can introduce a few seconds delay. This should be cached after the first invocation but wasn't for me in the past.

However, Gatekeeper shouldn't be triggered if you followed these steps: https://github.com/dennis-tra/alfred-dict.cc-workflow?tab=readme-ov-file#permissions (right click -> open -> confirm). This tells apple that you trust the binary. But I guess you've already done that :/

[dv0d]

Hi Dennis, sorry for the delay in responding. I did a bit more testing and noticed, that on my private laptop, it is indeed still super snappy. Seems there's an issue with my work's VPN, which might slow down the workflow. Guess I have to get used to that. :-/ But it's good to know that there's no restrictions on dict.cc side or whatnot. Keep it up!