I'm using translate-shell since few years and it has become an integral part of my software library.
Yesterday everything worked as usual, today I get since few hours this yellow bold text:
~$ tren "verwechseln" # alias tren='/usr/bin/trans de:en'
[ERROR] Google did not return results because rate limiting is in effect
[ERROR] Rate limiting
Didn't even know that few engines exist (I had apparently always 'auto' set), because I never had any issues with translate-shell and had only very basic needs without any audio functions etc...
I'd wonder myself if I'd be the only one experiencing this, anyway the sad thing is, that only Bing seems to work for me now (with 1-2s lagging though); aspell/hunspell return only similar-sounding bullshit instead of translations and yandex returns the same message as mentioned in #359 (which was opened btw. in 2020).
I am absolutely not an expert in network protocols, yet I suspect something that has to do with HTTP-vs-HTTPS requests respective blocking the former or so because I was just going to open another issue on some other CLI app which seems to be completely unusable because it's requests are blocked either by some used library or the public site/server it tries to connect to...maybe there's some connection between those.
I'm using translate-shell since few years and it has become an integral part of my software library.
Yesterday everything worked as usual, today I get since few hours this yellow bold text:
Didn't even know that few engines exist (I had apparently always 'auto' set), because I never had any issues with translate-shell and had only very basic needs without any audio functions etc...
I'd wonder myself if I'd be the only one experiencing this, anyway the sad thing is, that only Bing seems to work for me now (with 1-2s lagging though); aspell/hunspell return only similar-sounding bullshit instead of translations and yandex returns the same message as mentioned in #359 (which was opened btw. in 2020).
I am absolutely not an expert in network protocols, yet I suspect something that has to do with HTTP-vs-HTTPS requests respective blocking the former or so because I was just going to open another issue on some other CLI app which seems to be completely unusable because it's requests are blocked either by some used library or the public site/server it tries to connect to...maybe there's some connection between those.