Closed felixkempf closed 5 months ago
+1
+1
+1
+1
+1
+1
+1
Hey everyone, just here to ack that I've seen this issue. I'm currently travelling and can't really give an ETA when I'll be able to look into it. For reassurance, I'm using this workflow extensively myself so I'm definitely interested in a fix 👍
Okay, just had a quick look, and dict.cc
now returns the following message for requests made from Alfred:
Please don't run crawlers against dict.cc and don't try to make the dictionary available offline.
It's quite trivial to circumvent but because they seem to deliberately target this workflow with that warning message, I'll need to think about what to do. I might reach out to them and see if there's a way to find an agreement. However, this will take time and I guess the workflow is broken for now :/
Well, I changed my mind. This workflow is not crawling dict.cc nor making the dictionary available offline. It's doing regular queries.
When setting a user agent on the HTTP request the query works again. I'm making it transparent that the request comes from this workflow by setting the user agent to alfred-dict.cc-workflow
. If that's undesireable for dict.cc then they can easily block it again.
I guess this workflow is used by only a few hundred people anyway - shouldn't be a big deal. Check out this release: https://github.com/dennis-tra/alfred-dict.cc-workflow/releases/tag/v2.1.1
Thank you 🙏
Works flawlessly. Thank you for your time and effort
Thank you so much!
I'm not using this awesome workflow regularly, so I have no idea what change might have triggered it, but today I suddenly got
for every "word", with and without explicit languages, with all language pairs I tried.
macOS Monterey (12.7.4) Intel processor Alfred 5.5 [2257] workflow versions 2.0.0 and 2.1.0 Internet works fine and I can reach dict.cc in browser
See debug output below for some examples:
Is it something with my local setup? Any help appreciated